On Thu, Jan 28, 2010 at 04:17:41PM +0100, Beber wrote:
> So, do you guys plan to implement a such thing ? That's one of the
> features that is mostly missing imho. The principal miss in on client
> side as I have tools to manage packages but would like to not have too
> much specific scripts on cli
On Thu, 28 Jan 2010 16:17:41 +0100
Beber wrote:
> So, I did a wrapper to emerge --buildpkg to create tbz2 with SHA1 in
> names function of USE, like :
> CHOST="x86_64-pc-linux-gnu"
> ACCEPT_KEYWORDS="amd64"
> tcpdump
>
> USE="+chroot +ipv6 -ssl -test -samba -smi"
> is placed
> under
On Thu, Jan 28, 2010 at 04:17:41PM +0100, Beber wrote:
> So, I did a wrapper to emerge --buildpkg to create tbz2 with SHA1 in
> names function of USE, like :
> CHOST="x86_64-pc-linux-gnu"
> ACCEPT_KEYWORDS="amd64"
> tcpdump
>
> USE="+chroot +ipv6 -ssl -test -samba -smi"
> is placed unde
Hi,
I have a somewhat similar need and to satisfy it, I'm building packages
in a chroot that has all the common packages then one chroot per
variation. It's probably nowhere scalable enough for you though and
would most likely but much more efficient if package building could be
wrapped so that it
(I'm not an official developer.)
On Thu, Jan 28, 2010 at 10:17, Beber wrote:
> So, do you guys plan to implement a such thing ? That's one of the
> features that is mostly missing imho. The principal miss in on client
> side as I have tools to manage packages but would like to not have too
> much
Hi,
This mail is continuation of a discussion last month on IRC on
#gentoo-portage. As I think it's larger than just portage array, here it
is.
I have one server dedicated for compilation (xm-compile), and many
applicative servers (xmred5, lemonhead, etc).
Currently I use the --buildpkg on xm-co
