On Thu, 2005-03-10 at 14:41 +1300, Jerome Brown wrote:
> Is there a need for a seperate column? Would it not be eaiser to parse
> the profile name to extract that information. This would then allow you
> to search for all profiles that are valid for eg x86 BSD or alpha linux.
> Are there any situations where the arch and/or OS are not in the profile
> path? From a quick glance the non-default profiles (hardened, uclibc,
> embedded etc) do not specify a -linux in the profile which would mean
> either dropping the OS query, putting an OS column in or changing the
> profiles (which has the advantage of making them more consistant).

Personally, I would like seeing a profile structure similar to this:

$type/$os/$arch/$ver/$sub

Where:

$type is default, hardened, uclibc, etc
$os is linux, macos, bsd, etc
$arch is the architecture
$ver is the version the profile goes with and would be optional for
non-released projects/arches
$sub is any sub-profiles

This would require minor changes to a few profiles and would make things
pretty easy to maintain in the future.  It also gives a consistent
hierarchy that should meet any needs we have.

The only issue would be the temporary need to keep all of the older
profiles around until they were all deprecated and could be removed.

I would be willing to make these changes post-2005.0, as I don't think
anyone would let me live if we did another rebuild... ;]

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux