1 |
On 06/10/2016 08:00 AM, Ciaran McCreesh wrote: |
2 |
> On Thu, 9 Jun 2016 06:20:38 -0400 |
3 |
> Rich Freeman <rich0@g.o> wrote: |
4 |
>>> On 08/06/16 16:53, Rich Freeman wrote: |
5 |
>>>> Do you propose that you can have cross-repo dependencies? |
6 |
>>> Sure. This works well in Exherbo using Paludis. We could do it |
7 |
>>> right now if we wanted to. |
8 |
>>> |
9 |
>>>> If so that creates a lot of potential issues, even if you do it |
10 |
>>>> the NixOS way. |
11 |
>>> You should tell Exherbo and NixOS about all these issues that they |
12 |
>>> should be having but aren't having. |
13 |
>>> |
14 |
>> |
15 |
>> Perhaps you could explain how they actually prevent the issues I |
16 |
>> brought up? Since you didn't actually quote them I'll do so: |
17 |
>> |
18 |
>> Suppose you have 10 packages, and they each depend on zlib from a |
19 |
>> different repository? |
20 |
> |
21 |
> They don't. Packages do not depend upon "zlib from repository x". They |
22 |
> depend upon "zlib". |
23 |
> |
24 |
> The Exherbo model is not "packages are all over the place and there is |
25 |
> no coordination whatsoever". The model is "packages that lots of people |
26 |
> use are in a small number of core repositories and are carefully dealt |
27 |
> with to avoid breakages, |
28 |
|
29 |
Kinda like the @system + selected profile package list? |
30 |
|
31 |
|
32 |
> but packages that have small numbers of users |
33 |
> are in personal repositories which everyone can see". |
34 |
|
35 |
Yes. Right now I use my '/usr/local/portage' for dozens of packages. |
36 |
Maybe a hybrid of /usr/local/portage (being primary) and the public |
37 |
repo, when things are ready to share, or to get help on a personal |
38 |
package ebuild, by making it publically available? |
39 |
|
40 |
|
41 |
> Libraries and |
42 |
> packages that start to be used by many people get moved to one of the |
43 |
> central repositories; one way to tell that this needs to be done is |
44 |
> when it looks like the issues you think could happen actually start to |
45 |
> happen. |
46 |
|
47 |
And this effort needs a documentation collection to support users, post |
48 |
installation to their target (ideal stage-4?) collection of packages; |
49 |
many of which they maintain themselves even if a strong-user or dev |
50 |
helps them assimilate those final packages. Then they can use stage-4 |
51 |
snapshots for periodic backups on complete systems. or for quick |
52 |
installs of new systems. (that would super-charge my cluster dev work)! |
53 |
|
54 |
|
55 |
It just seems to me that we have all of that now, but it is:: |
56 |
1) not organized |
57 |
2) needs documentation so folks do not have to use irc to ask the same |
58 |
questions over and over and over again (gentoo wiki is maturing in this |
59 |
direction too, imho. |
60 |
3) needs (desires) gentoo managed repos, not github |
61 |
|
62 |
For now, we can use github for users. A glep or 2 can solved 1 and |
63 |
(2), well I was politely turned down, so suggestions on documentation |
64 |
to achieve this? Data-mining of emails and irc could easily provide |
65 |
the first-draft of the docs for need (2). |
66 |
|
67 |
|
68 |
|
69 |
James |