On Fri, 2004-08-13 at 17:22, William Hubbs wrote: > Hmmm, I guess I'm thinking that for general use the latest and greatest would be /default-linux/. > Any changes would be in /default-linux// for a while, then if it is decided that that change > should be made part of the profile for , it would be merged into that profile then the > /default-linux// profile would be depricated. > Its a good idea, but quite vague. What you are proposing is more or less what we do now ;) > I guess I'm seeing any subdirectory under /default-linux/ as either a special-purpose profile of > some kind, or a way to test changes to the profile before they are put into the main profile for that architecture. > Developers can use whatever name they want to for unoffical profiles: For example, a testing gcc3.4 profile (full dir layout here) /default-linux -x86 -/2005 -/2005.1 -/gcc34 Once that profile is stable and tested, it can be merged into a 2005.2. At that time we would deprecate the older profile if needed. I would really rather that we go the route that jhuebel proposed. It is not overly structured, but it gives enough structure as to keep our profile dir a bit more intuitive. If we document what is in each profile (default-linux/$arch/ChangeLog perhaps?) and stick to a standard naming scheme, I honestly believe that we will be better off in the long run. Consistency across the board is a Good Thing (TM). Cheers, -- John Davis Gentoo Linux Developer ---- GnuPG Public Key: Fingerprint: 4F9E 41F6 D072 5C1A 636C 2D46 B92C 4823 E281 41BB