1 |
On 2/13/21 4:53 PM, Zac Medico wrote: |
2 |
> On 2/13/21 4:37 PM, Zac Medico wrote: |
3 |
>> On 2/11/21 1:17 AM, Michał Górny wrote: |
4 |
>>> On Wed, 2021-02-10 at 19:51 +0100, Lars Wendler wrote: |
5 |
>>>> On Wed, 10 Feb 2021 19:57:48 +0200 Andreas K. Hüttel wrote: |
6 |
>>>> |
7 |
>>>>> Hi all, |
8 |
>>>>> |
9 |
>>>>> I'm announcing a new project here - "binhost" |
10 |
>>>>> |
11 |
>>>>> "The Gentoo Binhost project aims to provide readily installable, |
12 |
>>>>> precompiled packages for a subset of configurations, via central |
13 |
>>>>> binary package hosting. Currently we are still in the conceptual |
14 |
>>>>> planning stage. " |
15 |
>>>>> |
16 |
>>>>> https://wiki.gentoo.org/wiki/Project:Binhost |
17 |
>>>>> |
18 |
>>>>> If you're interested in helping out, feel free to add yourself on the |
19 |
>>>>> wiki page. |
20 |
>>>>> |
21 |
>>>>> Note that I see actually *building* the packages not as the central |
22 |
>>>>> point of the project (that could be e.g. a side effect of a |
23 |
>>>>> tinderbox). I'm more concerned about |
24 |
>>>>> * what configurations should we use |
25 |
>>>>> * what portage features are still needed or need improvements (e.g. |
26 |
>>>>> binpkg signing and verification) |
27 |
>>>>> * how should hosting look like |
28 |
>>>>> * and how we can test this on a limited scale before it goes "into |
29 |
>>>>> production" |
30 |
>>>>> * ... |
31 |
>>>>> |
32 |
>>>>> Comments, ideas, flamebaits? :D |
33 |
>>>>> |
34 |
>>>>> Cheers, |
35 |
>>>>> Andreas |
36 |
>>>>> |
37 |
>>>> |
38 |
>>>> It would be great to improve portage speed with handling binpkgs. I |
39 |
>>>> already have my own binhost for a couple of Gentoo systems and even |
40 |
>>>> though these systems don't have to compile anything themselves, |
41 |
>>>> installing ~100 to ~200 binpkgs takes way more than an hour of |
42 |
>>>> installation time. Arch Linux' pacman only takes a fraction of this |
43 |
>>>> time for the very same task. |
44 |
>>>> I know that I compare apples with pears here but even reducing the |
45 |
>>>> current portage time by 50% would be a huge improvement. |
46 |
>>> |
47 |
>>> Is that really a problem? For me, Portage takes about an hour just to |
48 |
>>> do the dependency processing these days. In fact, building from sources |
49 |
>>> is now faster than dependency calculations. |
50 |
>> |
51 |
>> The ratio of these times is dependent on the complexity of the |
52 |
>> dependencies involved, and so is the answer to your question. |
53 |
> |
54 |
> Also, in the context of binary packages, dependencies calculations are |
55 |
> generally simpler for binary packages because their USE conditionals and |
56 |
> slot-operator := dependencies are frozen in a particular state. This |
57 |
> dramatically reduces the search space involved in dependency calculation. |
58 |
|
59 |
IUSE_RUNTIME will obviously introduce conditionals in binary package |
60 |
dependencies, but we should welcome these conditionals because they will |
61 |
provide useful flexibility. |
62 |
|
63 |
I think IUSE_RUNTIME will be a very nice feature to have for project |
64 |
binhost, since it will allow binary package dependencies to behave with |
65 |
flexibility that more closely resembles the flexibility of ebuild |
66 |
dependencies. |
67 |
-- |
68 |
Thanks, |
69 |
Zac |