Currently, we have a new exheres profile layout in the tree. Now would probably be a good time to re-visit profile layout ideas.
Here's my proposal:
/profiles/
/base/
Same as it is now.
/$CHOST/
Basic (non-multilib) profile for the given CHOST.
parents = ../base
/$CHOST/multilib/
Multilib enabled profile for the given CHOST. This is
specifically for 32/64-bit C multilib stuff. Things like
perl/python/whatever will be in base.
parents = ..
/desktop/
Desktop-y things go here (like, default options that
include X, kde, gnome, etc). Maybe have sub-profiles
tailored towards specific desktop enironments.
/foo/
Useful defaults for 'foo'. Besides some 'server'-ish
profiles, I can't think of any other generic profiles to
ship, though.
So, someone who is running a multilib amd64 desktop might have:
profiles = ${location}/profiles/x86_64-pc-linux-gnu/multilib \
${location}/profiles/desktop
in their arbor.conf.
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.
Thoughts/suggestions?
--
Mike Kelly
signature.asc
Description: PGP signature
_______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
