Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)

[Aaron Walker <ka0ttic@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jerome Brown wrote:
> Aaron Walker wrote:
> <snip>
> 
>>In the case that I need this for (the eclectic profiles module), it'd be much
>>better IMO to be able to show valid profiles for a certain arch since a valid
>>profile for sparc is obviously not a valid profile for x86.
>>
>>Having a format of something like:
>>
>>alpha	default-linux/alpha/2004.3
>>alpha	default-linux/alpha/2005.0
>>...
>>x86	default-linux/x86/2004.3
>>...
>>
>>would be ideal IMO.
>>
>>comments?
> 
> 
> 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).
> 

There might be more, but the one I can think of off the top of my head is the
one for fbsd (keyword x86-fbsd) which is default-bsd/fbsd/x86.

I really wouldn't want to have to deal with special cases when you can just do
a simple sed call searching for lines beginning with $(portageq envvar ARCH).

- --
Slooly und soorely zee uneex crept up oon zee Neentendu user ...
Bork Bork Bork!

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCMEPkC3poscuANHARAscEAKDfJbtd/3gWNm9zKDwiV3IvbWmC9gCgiQcH
K5hqpeh77yrTFUw0vrYE0z8=
=RNdS
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list