Re: package configuration design
Hi,
>>"Joey" == Joey Hess <joey@kitenet.net> writes:
Joey> Well we already have a directory structure on the ftp site. The
Joey> problem is it's confusing. Is wget in net (makes ftp
Joey> connections) or web (makes www connections)? Is kernel-package
Joey> in admin (helps the admin do something) or devel (compiles
Joey> something) or misc? Is lilypond in sound (it typesets music and
Joey> can output .midi files) or tex (it can output tex files)?
__> find_section kernel-package
Section: misc
__> find_section wget
Section: web
__> find_section lilypond
Section: tex
What you are missing is a simple index scheme. Rather than
devolving back to primal chaos, we should implement a simple indexing
scheme to find where a package is.
In the simplest incarnation, it would be a file:
kernel-package: /some/place/there
lilypond: /another/location
Usin this simple scheme, dloc kernel-package would show you
the full path.
I do not find indexing a sufficient object to an organized
heirarchy for the config elements.
manoj
--
"Contrariwise", continued Tweedledee, "If it was so, it might be; and
if it were so, it would be; but as it isn't, it ain't. That's
logic." Lewis Carroll
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: