Well, I can define profiles with specific use flags and use profiles
to define which packages will be emerged in specific machines.
The subprofile thingy was for separating the desktop profile from the
server profile... from the server with apache/tomcat, server with
oracle... blablabla. Creating profiles for types of machines.
Using multiple chroot environments it's really a pain in the ass. Is
there no other way to do it?
On 10/30/06, Michelangelo <[EMAIL PROTECTED]> wrote:
Since one can have different use flags regardless of profiles i think
${pkg}-${profile}.tbz2 would not describe the USE flags used in compiling a
given package...maybe you meant to distinguish between archs...
But regarding to different archs I do miss the feature you're describing...
chrooting every different build is more work than I' willing to put in a
build system (i'm lazy I know)
regards
Michelangelo
2006/10/30, Sven Vermeulen <[EMAIL PROTECTED]>:
> José Costa said:
> > I'm trying to get a machine to compile a lot of binary packages to my
> > network and I can't figure out how to separate the same binary
> > packages with different use flags and I came up with some ideas and I
> > wanted to check with everyone if this is ok/nice/cool/forget.
> >
> > When we create binary packages they get the ${pkg}.tbz2 and they can
> > be overlapped by the same binary package with different use flags.
> >
> > How about using ${pkg}-${profile}.tbz2 and using the profiles to mark
> > them different?
>
> It is much easier to have your build systems build for just one profile,
> and use separate environments for different profiles. This doesn't require
> the builds to happen on different systems, I just use different chroot'ed
> environments for this (I first hoped to use UserMode Linux for this, but
> the additional overhead is too large).
>
> Wkr,
> Sven Vermeulen
>
> --
> [email protected] mailing list
>
>
--
[email protected] mailing list
