* [gentoo-dev] binary packaging
@ 2004-10-05 22:02 Philippe Trottier
2004-10-05 22:05 ` Ciaran McCreesh
0 siblings, 1 reply; 3+ messages in thread
From: Philippe Trottier @ 2004-10-05 22:02 UTC (permalink / raw
To: gentoo-dev
Hello,
I am trying to install a lot of systems using gentoo, so I did 4
machines with distcc to compile things, and the rest of the machines
will be using precompiled (emerge -k) I ran into some wierd suprises.
Then I had a chat on #gentoo-dev.
This is a resume...
It is somehow difficult to know and sort all the possible binary
packages. If the USE flags are different it does give some headache. One
suggestion is to had a hex bit mask for each USE flags. for example
package.w.x.y-rz-0A.tgz2 would mean USE flags are set as follow
00001010. At least that way someone can guess what package to fetch
without having 1000 char long file names.
But then repoman should make sure that if USE flags are changed then the
-r must also change. This won't tell what gcc has been used and may
other dependecies would cause troubles.
Now if someone uses xar, he could add all or the relevent parts of
emerge info in the archive. portage could make a sanity check and
recompile anyway if he thinks the package is too far. Other way to still
speed up the business would be to inject the precompiled data in ccache
directly. If the preprocessed code is the same and the compiler is the
same identical result are to be expected.
xar alone might prove difficult to handle, big file containing all,
loads of BW ... bad !
Subdirectories should be made under packages, at least separate them by
arch, I separate them by cpu-gentoo release , like athlon-mp-2004.2,
7400-2004.3, pentium4-1.4 etc etc works for me...
emerge -k ... seems not to care about PDEPEND for some reason, but I
might be doing something wierd.
If you have better ideas, please share them. Ill manage myself with the
current system anyway.
Yours,
Philippe
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] binary packaging
2004-10-05 22:02 [gentoo-dev] binary packaging Philippe Trottier
@ 2004-10-05 22:05 ` Ciaran McCreesh
2004-10-10 9:26 ` Paul de Vrieze
0 siblings, 1 reply; 3+ messages in thread
From: Ciaran McCreesh @ 2004-10-05 22:05 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Wed, 06 Oct 2004 01:02:42 +0300 Philippe Trottier
<tchiwam@gentoo.org> wrote:
| It is somehow difficult to know and sort all the possible binary
| packages. If the USE flags are different it does give some headache.
| One suggestion is to had a hex bit mask for each USE flags. for
| example package.w.x.y-rz-0A.tgz2 would mean USE flags are set as
| follow 00001010. At least that way someone can guess what package to
| fetch without having 1000 char long file names.
Ick. The way to do this that won't break things is to decide upon a set
of USE flags, apply them at a global level and then make a set of
binaries for said combination. Then, give it a name and stick a file
named __make.conf__ in the binaries directory. There's probably some way
to do this neatly using the stuff in GLEP 29 if you really want.
Incidentally, you'd to do the same for CFLAGS that you do for USE. For
certain CFLAGS you can't safely mix combinations, it's an all or nothing
thing.
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] binary packaging
2004-10-05 22:05 ` Ciaran McCreesh
@ 2004-10-10 9:26 ` Paul de Vrieze
0 siblings, 0 replies; 3+ messages in thread
From: Paul de Vrieze @ 2004-10-10 9:26 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Wednesday 06 October 2004 00:05, Ciaran McCreesh wrote:
> Ick. The way to do this that won't break things is to decide upon a set
> of USE flags, apply them at a global level and then make a set of
> binaries for said combination. Then, give it a name and stick a file
> named __make.conf__ in the binaries directory. There's probably some way
> to do this neatly using the stuff in GLEP 29 if you really want.
>
> Incidentally, you'd to do the same for CFLAGS that you do for USE. For
> certain CFLAGS you can't safely mix combinations, it's an all or nothing
> thing.
Which exactly shows why binary packaging can be a bitch and the reason that
even debian must use releases. Source based can mix and match, but binaries
are never that flexible.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-10-10 9:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-05 22:02 [gentoo-dev] binary packaging Philippe Trottier
2004-10-05 22:05 ` Ciaran McCreesh
2004-10-10 9:26 ` Paul de Vrieze
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox