Mike Kelly wrote:
So, someone who is running a multilib amd64 desktop might have:
profiles = ${location}/profiles/x86_64-pc-linux-gnu/multilib \
${location}/profiles/desktop
Is there actually a point of specifying the whole path?
We could also make the profile location relative to the profiles/ dir in
that repo:
profiles = x86_64-pc-linux-gnu/multilib desktop
And if necessary, there could be a setting profiles dir, which defines
where to look for profiles, just like we have setsdir, newsdir...
Another thing which I think might be good to clean things up, would be
to split the CHOST profile stuff out of the normal setting.
I'd say that the CHOST profiles go into profiles/arch/${CHOST} and
introduce a setting profiles_arch (could also be named arch or similar),
which would be set to that:
profiles_arch = x86_64-pc-linux-gnu/multilib
This setting would be mandatory, while the other profiles setting would
be optional, and can be set to desktop, server...
We could also move the desktop, server... profiles to a subdir, like the
arch profiles, but I don't know a good name for such a dir/setting
(maybe profiles/flavour/ and profiles_flavour?).
Using that, the above example would look like this:
profilesdir = ${location}/profiles (optional, default is
${location}/profiles)
profiles_arch = x86_64-pc-linux-gnu/multilib
profiles_flavour = desktop (optional, default is none)
Maybe(!) it would also be easier to prevent that people try to set both
x86_64-pc-linux-gnu and x86-pc-linux-gnu (or similar)?
We may or may not want to someday have versioned profiles for some of
these things (like the /2007.0/ stuff Gentoo does). I'm leaning towards
not seeing the point of those currently.
Is there actually a point in having versioned profiles at all?
_______________________________________________
Exherbo-dev mailing list
[email protected]
http://lists.exherbo.org/mailman/listinfo/exherbo-dev
