public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: GLEP 19: Gentoo Stable Portage Tree -- ideas
Date: Sun, 08 Jan 2006 10:55:50 -0600	[thread overview]
Message-ID: <43C14416.9050106@gentoo.org> (raw)
In-Reply-To: <1136729665.30850.5.camel@inertia.twi-31o2.org>

[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]

Chris Gianelloni wrote:
> On Fri, 2006-01-06 at 17:32 -0600, Lance Albertson wrote:
> 
>><snip a bunch about binpkg>
>>
>>I think a key thing that is missing is build info that is only kept on
>>the installed system. If we were to ever create a build server setup, we
>>need to be able to have multiple binpkg's of the same version depending
>>on differences between sub-arch, use flags, cflag differences, gcc
>>version differences, etc. The key one i'm after is use flags. I'm not
>>sure of the technical details behind it, but we need something to make
>>the binpkgs more useful outside of the local system. Having the ebuild
>>packed at the end is a great idea! I think its just time to extend the
>>format to include more and possibly add things for build servers.
> 
> 
> USE flags are stored in the package.  The main thing is that portage
> doesn't consider them, at all, unless you use --newuse, in which case if
> the USE flags do not match, it will not use the package and will compile
> from source.  We use this every day in Release Engineering with
> catalyst.

That maybe true, but if you're going to use such things on a build
server, you need to be able to have multiple tars of the same package
for the different use flags you may use. Maybe for one server setup I
need useflag foo, but another setup I don't need it. This central
repository needs to differentiate between those two needs. I know you
could make two separate binpkg dirs for those cases, but thats not
scalable at all. I was looking for something more generic.

To summarize, differentiating use flags in gentoo binary packages isn't
very scalable at the moment. A few rough ideas that just popped in my
head is either packing all of these versions into one tarball (not even
sure if thats feasible), or creating a hashed suffix based upon the
useflags enabled/disabled at the time that you append to the tarball name.

-- 
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager

---
GPG Public Key:  <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1  4D07 416F A15D 27F4 B742

ramereth/irc.freenode.net

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-01-08 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06  4:42 [gentoo-dev] GLEP 19: Gentoo Stable Portage Tree -- ideas Andrew Muraco
2006-01-06  4:52 ` Andrew Muraco
2006-01-06  5:29   ` Brian Harring
2006-01-06  5:35 ` Brian Harring
2006-01-06  9:00   ` Chris Bainbridge
2006-01-06  9:36     ` [gentoo-dev] " Duncan
2006-01-06 15:09       ` Chris Gianelloni
2006-01-06 15:27         ` Lance Albertson
2006-01-06 16:19           ` Carsten Lohrke
2006-01-06 18:59             ` Chris Gianelloni
2006-01-06 16:46           ` Grant Goodyear
2006-01-06 17:12             ` Grant Goodyear
2006-01-08  0:24             ` Stuart Herbert
2006-01-06 17:25           ` Brian Harring
2006-01-06 18:41           ` Donnie Berkholz
2006-01-06 18:57           ` Chris Gianelloni
2006-01-06 15:05     ` [gentoo-dev] " Chris Gianelloni
2006-01-06 17:39       ` Brian Harring
2006-01-06 19:30         ` Chris Gianelloni
2006-01-06 22:48           ` [gentoo-dev] " Duncan
2006-01-06 23:32             ` Lance Albertson
2006-01-08 14:14               ` Chris Gianelloni
2006-01-08 16:55                 ` Lance Albertson [this message]
2006-01-08 17:19                   ` Brian Harring
2006-01-08 17:26                     ` Lance Albertson
2006-01-06 23:11         ` [gentoo-dev] " Olivier Crete
2006-01-08 14:12           ` Chris Gianelloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C14416.9050106@gentoo.org \
    --to=ramereth@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox