Re: category

<[email protected]> wrote:
>> As the /package page states, the reason for classifying packages is
>> simply to keep the directory from getting too big.  With that in
>> mind, why agonize over how to classify packages when it has already
>> been done?  For example, Debian GNU/Linux and FreeBSD already have
>> a huge selection of packages that are classified by category:
>
> But I am, for example, using linuxfromscratch, where catogories
> aren't.

That's irrelevant.  The point above was that *any* already-implemented
categorization could be used for slashpackage.  Then anyone using
slashpackage would get that categorization scheme, even if the rest of
their system didn't use it.

> What I was talking about is, that I may put windowmaker in gui, but
> somebody other put it into sys. And now, if third package cannot
> exactly say, where it should look for libwraster library (provided
> by windowmaker).

This is why package paths should be registered by the package
maintainers.  Do not expect to get the full benefits of slashpackage
if you ignore the global registry.

> But I have never seen note about slashpackage on sites like php.net.

You could encourage them to participate by registering a name for PHP.

> Btw. why is not qmail in /package/mail/qmail ?

qmail 1.03 predates slashpackage, and qmail 2 isn't finished yet.


paul