Re: on slashpackage hierarchy

--0015174c17d896aca5049332198d
Content-Type: text/plain; charset=UTF-8

Hi;

in my public tarball and html archives, i use the [a-z0]/ followed by a
proper name;
the name is always descriptive of the directory content.

For my pkg/ tree where code is placed, i use pkg/name/version/ generally;
this is also how the Toastball (qv) pkg manager sets things up.

- If you don't ask a question, you get nothing.

- to not see and believe is better than to see and not believe.

*** Note Well: This email address is private and may NOT be used nor
redistributed to third parties for the purpose of sending me information
that I have NOT requested.  Any use of this email address without *MY*
explicit permission will be considered a Trespass and may result in a
Monetary consequences.


On Sun, Oct 17, 2010 at 12:48, Zenaan Harkness <[email protected]> wrote:

> re "Why classify packages at all? Why admin/daemontools instead of
> simply daemontools? The answer is simply that many people complain
> when a single directory gets too big. "
>
> I used to classify by categories, my downloaded software (/setups) and
> downloaded documentation (/setups/doc/), as well as my own work
> documents (~/work/ - letters, legal documents for many people I have
> assisted, and other work products).
>
> Problem: Categories overlap (eg web, mail, net), often horribly (same eg.).
>
> Problem: Newer created categories may be 'more appropriate' for a
> package previously assigned to a different category.
>
> Problem: Package management tools must first map from package name to
> category name, before locating a named package (eg. user wants to show
> "package-status djbdns").
>
> 1)
> Underlying dynamic: human need for complexity management tools.
>
> Categorization is a legitimate complexity management tool.
>
> Alphabet single-letter directories is a legitimate complexity management
> tool.
>  - Eg: Debian's pool/ package hierarchy
>  - debian also use liba/, libb/ etc, since so many libs they messed up l/
>
> I changed my /setups/*category* (setups = software downloads) and
> /setups/doc/*category*, and /work/*category*, to be as follows:
> /setups/[0-9a-z]/*
> /setups/doc/[0-9a-z]/*
> /work/[0-9a-z]/*
>
> ~/work example:
> ~/work/m/matter/[au|us|etc]/[a-z]/*
>
> eg:
> ~/work/f/forms/*
> ~/work/m/matter/au/h/harkness-zenaan/*
> ~/work/m/matter/au/s/smith-john/*
>
> In my case, country (au|us) is a category, and then the alphabetical
> by surname. This works very well for me; makes it easy to locate a
> particular client's work products.
>
> Alphabetical directories are a desirable complexity management tool to
> me, once I hit more than about 50 entries in a directory. Filesystem
> navigation/ tab completion works well for me.
>
> Since I'm on GNU system, I can and do use symlinks to add in
> categories as well, as a convenience, in my /setups/ hierarchy.
>
> If I were to use /package or similar, I would not use it without this
> debian-style alphabetical directories complexity management tool. I
> would have:
> /package/a/*
> /package/b/*
> etc
>
> If you included such a recommendation in your slashpackage docs, I
> might use /package. If you recommended against doing so, I would use a
> different /apps directory. An alphabetical organization does not
> conflict with your categorization organization.
> Alphabetical means 26 extra directories inside /package (or eg /apps).
>
> Alphabetical means low cognitive overhead. I know default installed
> djbdns can be found at:
>  /package/d/djbdns/*
>
> This is desirable not only for humans, but also for automated tools/
> package management tools. Eg debian's
>  - "apt-cache show djbdns"
> would not have to first map from package name to category name, just
> to find the package, but can instead just go to /package/d/...
>
> (I imagine /package/d/unversioned-name/META/ might be a good standard
> for metadata location; but that's another conversation/ process.)
>
> Feedback sought,
> Zenaan
>

--0015174c17d896aca5049332198d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi;<br><br>in my public tarball and html archives, i use the [a-z0]/ follow=
ed by a proper name;<br>the name is always descriptive of the directory con=
tent.<br><br>For my pkg/ tree where code is placed, i use pkg/name/version/=
 generally; this is also how the Toastball (qv) pkg manager sets things up.=
<br clear=3D"all">

<br>- If you don&#39;t ask a question, you get nothing.<br><br>- to not see=
 and believe is better than to see and not believe.<br><br>*** Note Well: T=
his email address is private and may NOT be used nor redistributed to third=
 parties for the purpose of sending me information that I have NOT requeste=
d.=C2=A0 Any use of this email address without *MY* explicit permission wil=
l be considered a Trespass and may result in a Monetary consequences.<br>


<br><br><div class=3D"gmail_quote">On Sun, Oct 17, 2010 at 12:48, Zenaan Ha=
rkness <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">zen@freedb=
ms.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddi=
ng-left: 1ex;">

re &quot;Why classify packages at all? Why admin/daemontools instead of<br>
simply daemontools? The answer is simply that many people complain<br>
when a single directory gets too big. &quot;<br>
<br>
I used to classify by categories, my downloaded software (/setups) and<br>
downloaded documentation (/setups/doc/), as well as my own work<br>
documents (~/work/ - letters, legal documents for many people I have<br>
assisted, and other work products).<br>
<br>
Problem: Categories overlap (eg web, mail, net), often horribly (same eg.).=
<br>
<br>
Problem: Newer created categories may be &#39;more appropriate&#39; for a<b=
r>
package previously assigned to a different category.<br>
<br>
Problem: Package management tools must first map from package name to<br>
category name, before locating a named package (eg. user wants to show<br>
&quot;package-status djbdns&quot;).<br>
<br>
1)<br>
Underlying dynamic: human need for complexity management tools.<br>
<br>
Categorization is a legitimate complexity management tool.<br>
<br>
Alphabet single-letter directories is a legitimate complexity management to=
ol.<br>
=C2=A0- Eg: Debian&#39;s pool/ package hierarchy<br>
=C2=A0- debian also use liba/, libb/ etc, since so many libs they messed up=
 l/<br>
<br>
I changed my /setups/*category* (setups =3D software downloads) and<br>
/setups/doc/*category*, and /work/*category*, to be as follows:<br>
/setups/[0-9a-z]/*<br>
/setups/doc/[0-9a-z]/*<br>
/work/[0-9a-z]/*<br>
<br>
~/work example:<br>
~/work/m/matter/[au|us|etc]/[a-z]/*<br>
<br>
eg:<br>
~/work/f/forms/*<br>
~/work/m/matter/au/h/harkness-zenaan/*<br>
~/work/m/matter/au/s/smith-john/*<br>
<br>
In my case, country (au|us) is a category, and then the alphabetical<br>
by surname. This works very well for me; makes it easy to locate a<br>
particular client&#39;s work products.<br>
<br>
Alphabetical directories are a desirable complexity management tool to<br>
me, once I hit more than about 50 entries in a directory. Filesystem<br>
navigation/ tab completion works well for me.<br>
<br>
Since I&#39;m on GNU system, I can and do use symlinks to add in<br>
categories as well, as a convenience, in my /setups/ hierarchy.<br>
<br>
If I were to use /package or similar, I would not use it without this<br>
debian-style alphabetical directories complexity management tool. I<br>
would have:<br>
/package/a/*<br>
/package/b/*<br>
etc<br>
<br>
If you included such a recommendation in your slashpackage docs, I<br>
might use /package. If you recommended against doing so, I would use a<br>
different /apps directory. An alphabetical organization does not<br>
conflict with your categorization organization.<br>
Alphabetical means 26 extra directories inside /package (or eg /apps).<br>
<br>
Alphabetical means low cognitive overhead. I know default installed<br>
djbdns can be found at:<br>
=C2=A0/package/d/djbdns/*<br>
<br>
This is desirable not only for humans, but also for automated tools/<br>
package management tools. Eg debian&#39;s<br>
=C2=A0- &quot;apt-cache show djbdns&quot;<br>
would not have to first map from package name to category name, just<br>
to find the package, but can instead just go to /package/d/...<br>
<br>
(I imagine /package/d/unversioned-name/META/ might be a good standard<br>
for metadata location; but that&#39;s another conversation/ process.)<br>
<br>
Feedback sought,<br>
<font color=3D"#888888">Zenaan<br>
</font></blockquote></div><br>

--0015174c17d896aca5049332198d--