From: Justin Y. <ju...@sk...> - 2003-03-26 04:10:25
|
On Tue, 2003-03-25 at 20:38, Jason Long wrote: > Justin, > > I'm attaching what I have so far, for you to take a look at. Some of it is > repeat of stuff that's already implemented or discussed. A few questions/suggestions: - In the identifier, could we drop the .type or make it optional? i.e., config4gnu.sourceforge.net/samba-config#samba-share, or maybe even just do samba-config#samba-share and if no top level is specified then config4gnu.sourceforge.net is assumed? Not sure if this would cause a problem, just wondering about saving some extra typing. - If I reference config4gnu.sourceforge.net/samba-config.type#samba-share, do all of samba-config.type's types get loaded, or just samba-share? - Is there a way to include another type definition from within a .type file, i.e., trigger the load_type_definition_file function? - If I extend a type, I assume its type file gets parsed, and I assume it must be specified by its ID. Do all the types in that .type file get added to the current list of available types (so that they can be referenced as if they were types in the current file), unless of course they're overridden in the current .type file? - I assume that if the current type file has a type that it would never be over-ridden by anything which is extended, included, or referenced within that type definition file? I could understand if including were required to be done first, and maybe even extending, but referencing causing overriding would be a problem. I'll modify the things you suggested about my proposal. My only question is who should the owner of a file be? The current user I assume (and maybe root in the case of an eventual system-wide cache directory)? Justin -- SkiingYAC Custom Solutions http://www.SkiingYAC.com |