1 |
On Sunday 25 July 2004 11:22, Pieter Van den Abeele wrote: |
2 |
> On 25 Jul 2004, at 03:26, Jason Stubbs wrote: |
3 |
> > The real problem is that nobody (if I am like everybody else) has |
4 |
> > heard about this stuff except those that are following the macos movement. |
5 |
> > If you had announced your plan to inject everything in MacOS and keyword |
6 |
> > ebuilds on the assumption that those packages are available, many people |
7 |
> > could have told you that the issues that are happening currently would |
8 |
> > occur. More importantly, solutions would have been able to be created |
9 |
> > before the current issues became issues. |
10 |
> |
11 |
> The MacOS project was announced one year ago. One single portage |
12 |
> feature that still isn't implemented held the project up for that long. |
13 |
|
14 |
Bug #? If there is in fact a bug, it's not marked as a blocker or even as |
15 |
being critical. |
16 |
|
17 |
> It's a relatively simple feature compared to the other requirements I |
18 |
> have for a next generation portage. |
19 |
|
20 |
So you're planning to fork the project? |
21 |
|
22 |
> What MacOS is doing right now is moving forward and identifying all MacOS |
23 |
> related issues, creating bug reports for them and we try to do our best |
24 |
> finding both long term and short term solutions. We can't afford to be put |
25 |
> on hold for another year, unfortunately. |
26 |
|
27 |
I've been an official developer for just over five months, and have been |
28 |
working on portage and hanging out in #gentoo-portage and on the |
29 |
gentoo-portage-dev list for about nine months yet I haven't heard any |
30 |
discussion whatsoever about what is required to support portage on macos. |
31 |
THAT is what has held it up for a year. |
32 |
|
33 |
> >> Why does repoman/linux think the dependency graph for macos is broken. |
34 |
> > |
35 |
> > Because it is. |
36 |
> |
37 |
> By design. |
38 |
|
39 |
As I said above, no reason had been shown to change the design. |
40 |
|
41 |
> > So then you are trying to use one keyword to describe both a situation |
42 |
> > where all base packages are available and one where they aren't? |
43 |
> |
44 |
> darwin keyword + darwin profiles -> from scratch approach, |
45 |
> bootstrapping, livecds, nothing which depends on xcode |
46 |
> macos keyword + macos profiles -> repository of mac OS X compatible |
47 |
> apps, supports forced overwrites, supports prefixed installs, no |
48 |
> bootstrapping |
49 |
> |
50 |
> anything that is darwin compatible is macos compatible, but not the |
51 |
> other way around. |
52 |
|
53 |
That seems fine. |
54 |
|
55 |
> >> Since repoman doesn't complain about macos under macos (it must be |
56 |
> >> broken or somehow take into account injected packages when doing |
57 |
> >> --emptytree), I prefer this option. It's also the least amount of |
58 |
> >> work. |
59 |
> > |
60 |
> > Does it complain when the patch Travis mentioned is in place? |
61 |
> |
62 |
> I'll try. |
63 |
> |
64 |
> I must say that repoman doesn't work out of the box on any of my |
65 |
> computers. You're free to try it yourself, I was quite surprised to see |
66 |
> repoman being happy about macos keywords on my x86, ppc and sparc |
67 |
> machines. All running latest portage development release .51_pre13. |
68 |
|
69 |
Yes, repoman is quite buggy. That is no reason to use it as a scapegoat. |
70 |
|
71 |
> >> 2. make repoman macos aware |
72 |
> > |
73 |
> > s/make repoman macos aware/include support in ALL of portage/ |
74 |
> |
75 |
> That's the plan. There will be code, no worry. But until there's code, |
76 |
> we use the cleanest possible short-term solution for various issues. |
77 |
|
78 |
Again, by forking? |
79 |
|
80 |
> >> This requires new portage features. Adding another file to the |
81 |
> >> profiles, I can think of at least 2 portage feature requests that |
82 |
> >> require adding another file to the profiles, so this can't be a short |
83 |
> >> term solution. |
84 |
> > |
85 |
> > Why wasn't this suggested months ago? A feature such as this (which |
86 |
> > isn't hard to implement btw) could allow you to not inject everything and |
87 |
> > be able satisfy repoman as well. It would also be useful in separating |
88 |
> > your two types of macos users into separate profiles. |
89 |
> |
90 |
> When I openened the bug about persistent packages, somebody masked it |
91 |
> as a DUP for a bug numbered somewhere between 11000 - 12000 (we're at |
92 |
> 54000 right now). I'm assuming similar feature requests have been |
93 |
> waiting for some time. |
94 |
|
95 |
Please give bug numbers. I want the facts first-hand. |
96 |
|
97 |
Regards, |
98 |
Jason Stubbs |
99 |
|
100 |
-- |
101 |
gentoo-dev@g.o mailing list |