1 |
We would need portage to generate packages with an additional "manifest" file |
2 |
in it or in a package format that could hold meta-information in some way |
3 |
such as: |
4 |
|
5 |
USE flags enabled in this package (only the ones relevant to the particuliar |
6 |
package) |
7 |
|
8 |
Portage's PROFILE (default-x86-1.4 for example) |
9 |
|
10 |
CHOST / CFLAGS used to compile the package, if relevant. |
11 |
|
12 |
|
13 |
Then a binary enabled portage would contact a master server and ask for a |
14 |
binary package compiled with the right combination of USE flags, profile and |
15 |
CHOST and if it exists download it and install it, and if it does not compile |
16 |
it from the sources.. |
17 |
|
18 |
|
19 |
|
20 |
Cedric |
21 |
|
22 |
|
23 |
|
24 |
|
25 |
|
26 |
Le 10 Avril 2003 03:27, Spider a écrit : |
27 |
> begin quote |
28 |
> On Thu, 10 Apr 2003 00:13:30 +0000 |
29 |
> |
30 |
> Noah Justin Norris <gentoo@×××××.com> wrote: |
31 |
> > Is there any interest to start a binary release of gentoo with |
32 |
> > precompiled |
33 |
> > binaries. Im talking the entire source tree i know many people that |
34 |
> > would switch to gentoo if they would not have to compile every thing |
35 |
> > from source . not everyone has the fastest computer out there. |
36 |
> |
37 |
> Well, thats one thing thats an interesting idea, another would be to |
38 |
> track our "stable" tree and keep updating the system of GRP binaries to |
39 |
> provide for this.. do note that this means that a system cannot be used |
40 |
> for testing things in a "normal" way (installing odd things that might |
41 |
> be dependencies or not) |
42 |
> |
43 |
> |
44 |
> To do the whole tree as binary is an impossibility, if nothing else so |
45 |
> for license issues. But continuously providing it could be a welcome |
46 |
> service. |
47 |
> |
48 |
> I know I'd welcome it, as a far simpler way of installing and keeping my |
49 |
> celeron running.. But I think it'd require some more portage hacking |
50 |
> to "make it work", at least the following. |
51 |
> |
52 |
> a) package signing |
53 |
> b) configured default binary locations |
54 |
> c) binary-vs-source preference |
55 |
> |
56 |
> |
57 |
> to do more than one set of USE flags would be overkill imo, and harder |
58 |
> to implement in "true" form. |
59 |
> |
60 |
> |
61 |
> //Spider |
62 |
|
63 |
|
64 |
-- |
65 |
gentoo-dev@g.o mailing list |