| 1 |
Chris Gianelloni wrote: |
| 2 |
> On Fri, 2006-01-06 at 17:32 -0600, Lance Albertson wrote: |
| 3 |
> |
| 4 |
>><snip a bunch about binpkg> |
| 5 |
>> |
| 6 |
>>I think a key thing that is missing is build info that is only kept on |
| 7 |
>>the installed system. If we were to ever create a build server setup, we |
| 8 |
>>need to be able to have multiple binpkg's of the same version depending |
| 9 |
>>on differences between sub-arch, use flags, cflag differences, gcc |
| 10 |
>>version differences, etc. The key one i'm after is use flags. I'm not |
| 11 |
>>sure of the technical details behind it, but we need something to make |
| 12 |
>>the binpkgs more useful outside of the local system. Having the ebuild |
| 13 |
>>packed at the end is a great idea! I think its just time to extend the |
| 14 |
>>format to include more and possibly add things for build servers. |
| 15 |
> |
| 16 |
> |
| 17 |
> USE flags are stored in the package. The main thing is that portage |
| 18 |
> doesn't consider them, at all, unless you use --newuse, in which case if |
| 19 |
> the USE flags do not match, it will not use the package and will compile |
| 20 |
> from source. We use this every day in Release Engineering with |
| 21 |
> catalyst. |
| 22 |
|
| 23 |
That maybe true, but if you're going to use such things on a build |
| 24 |
server, you need to be able to have multiple tars of the same package |
| 25 |
for the different use flags you may use. Maybe for one server setup I |
| 26 |
need useflag foo, but another setup I don't need it. This central |
| 27 |
repository needs to differentiate between those two needs. I know you |
| 28 |
could make two separate binpkg dirs for those cases, but thats not |
| 29 |
scalable at all. I was looking for something more generic. |
| 30 |
|
| 31 |
To summarize, differentiating use flags in gentoo binary packages isn't |
| 32 |
very scalable at the moment. A few rough ideas that just popped in my |
| 33 |
head is either packing all of these versions into one tarball (not even |
| 34 |
sure if thats feasible), or creating a hashed suffix based upon the |
| 35 |
useflags enabled/disabled at the time that you append to the tarball name. |
| 36 |
|
| 37 |
-- |
| 38 |
Lance Albertson <ramereth@g.o> |
| 39 |
Gentoo Infrastructure | Operations Manager |
| 40 |
|
| 41 |
--- |
| 42 |
GPG Public Key: <http://www.ramereth.net/lance.asc> |
| 43 |
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 |
| 44 |
|
| 45 |
ramereth/irc.freenode.net |
Archives