2008/4/9 Damien Cassou <damien.cassou at gmail.com>:
> On Wed, Apr 9, 2008 at 8:21 AM, Igor Stasenko <siguctua at gmail.com> wrote:
>  >  What i like in above, that it's self-explanatory, easy to find and
>  >  don't requires extra UI/GUI to manage package.
>
>  But users needs a UI to install new packages.
>

Yes, of course but it's more or less trivial - show a list and add some actions.
What is not trivial is to create UI to build own packages, when
developer need to create new package and include all required info.
This is unnecessary if developer simply needs to define a method which
describes package.
It is also can be extended very simply. Suppose i want to include
information that given package is successor of older package and
provides similar functionality but with new design under new brand. It
could be done as simple as writing:
info ancestors: #( 'Foo' ).

Adding maturity level:
info maturity: #beta.

I didn't looked yet at Sake, but if each package contains something
like 'printDescription: stream' method, again, it's easy for developer
to override this method and include new fields which will be showed to
users.

>
>  --
>  Damien Cassou
>  Peter von der Ahé: «I'm beginning to see why Gilad wished us good
>  luck». (http://blogs.sun.com/ahe/entry/override_snafu)
>
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.