Re: package configuration design
Hi,
>>"Wichert" == Wichert Akkerman <wichert@wiggy.ml.org> writes:
Wichert> [1 <text/plain; us-ascii (7bit)>]
Wichert> Previously Manoj Srivastava wrote:
>> Hmm. I wonder. Is there areason for a flat heirarchy? Could
>> deeper nesting have value? For example, there could be a "folder"
>> called MUA (or something), and all mail user agents go there, a
>> higher level value (/top/mua/mailhosthostname) can be over ridden by
>> /top/mua/vm/mailhostname); it allows a group of packages to share a
>> default.
Wichert> Hmm, looks like I deleted something too much in rewriting the text.
Wichert> But the idea was that packages can have their own hieararchy. Only all
Wichert> packages are under the same root, to make it easier to find their
Wichert> information.
Actuall, maybe we should reconsider even that. The ast time I
updated apt, 2200+ packages were updated. Having them in a flat
folder is not likely to help browsing (heck, even a simple ls in
/usr/doc takes perceptible time).
I would much rather we assigned more structure to the set of
packages, and allow for a greater facility for grouping packages and
scoping common variables (all MUA's and News readers can then have a
mail-from variable in common, all news readers would share an NNTP
server address; but a news reader could have an over ride: so all but
one news readers read from the local spool, and one has an fast
minimalist off-site ews reader).
To the point that this makes packages harder to find, I say
that a simple index (<package name>: Location set of lines in an
index file) would in fact be faster; we can invest in DB based index
files files if speed were an issue.
I think that flat databases are not really scalable.
manoj
--
I do not call him a brahmin who is so by natural birth from his
mother. He is just a supercilious person if he still has possessions
of his own. He who owns nothing of his own, and is without attachment
- that is what I call a brahmin. 396
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: