Hello David, Sorry for the pause :-)
There is a picture that is becoming clearer and clearer from your posts. I will quote your post slightly out of sequence to bring some focus to this: -----Original Message----- From: David Douthitt <[EMAIL PROTECTED]> To: Serge Caron <[EMAIL PROTECTED]>; LEAF Development <[EMAIL PROTECTED]> Date: February 23, 2002 10:14 PM Subject: Re: [Leaf-devel] Re: Standards and due process :-) [out of sequence :)] > >> Clearly, LEAF is designed to allow packages to overwite each other's >files. > >Not designed to. It's just that the more capabilities you put into You are working under the premise that a file has one and only one package of residence. Please note that this is an observation and not a value judgment of any kind: AFAIK, there is nothing wrong with this premise. The natural consequence of this premise is that packages can be loaded in an indeterminate order since, under this premise, there is no name space conflict between packages. Hence [out of sequence :)] > >In Dachstein the load order is explicitly stated; in Oxygen the load >order is indeterminate (since all packages are loaded automatically). > You do not enforce this premise: [out of sequence :)] >the packaging, the more space it takes up. Bullet-proofing, >dependency checking, space checking, menu interfaces - it all takes up >space. apkg is more powerful than lrpkg (I'd say) and I suspect it's Some files are duplicated in config.lrp... [out of sequence :)] >> Is the intent of your post to demonstrate that Oxygen >> already has a default store, albeit one reserved to *.conf >> files? > >I don't know if you'd call it a "default store" - it's a way of >configuring the system so you can boot from CDROM. ...as you noted elsewhere, this single package is loaded last and is therefore excluded from possible name space conflicts since it is processed differently than any other package. This does not impact your premise. > >However.... even with the original idea, root.lrp was NOT supposed to >change. So the only things that will show up in any package defined >by "./" will be files that SHOULD be in another package.... > This is a not a natural consequence of your premise. You are implictly claiming that there is a mapping of the entire file system into LEAF/LRP packages for everybody to consult. You are also claiming that it is an error to store in root.lrp any contents other than what you designed in. The former claim is Michael's quest: if there is such a mapping, where can we consult it and where is the body that will manage such a beast? If there is no such mapping, where are the guidelines in designing a package? The later claim means that the base system is not extensible. Is my understanding correct? Regards, Serge Caron _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
