1 |
On Fri, 2005-04-29 at 09:25 -0400, Dan Meltzer wrote: |
2 |
> The problem with ebuild config, at least until bug 11359 is handled, |
3 |
> is if the package is emerged early on in a list of packages, there is |
4 |
> a chance the person won't know to use ebuild config.... would it be |
5 |
> possible for portage to run an ebuild config for _all_ packages that |
6 |
> need it after _all_ packages that are being emerged are emerged? This |
7 |
> way the upgrade goes without interference, but the customization waits |
8 |
> until the person comes back, either that or an emerge config that |
9 |
> tracks all packages that need config that have yet to be configged, |
10 |
> currently, hoping a person thinks to ebuild packagename config is a |
11 |
> lot to ask, unless every package takes use of it... |
12 |
|
13 |
My opinion: |
14 |
|
15 |
I really don't care. |
16 |
|
17 |
We aren't doing anything in the config sections that cannot be done |
18 |
manually, we're just making it easier by scripting it into a single |
19 |
place. As more and more packages make use of the mechanism, people will |
20 |
become used to using it. If someone doesn't use it, they won't have a |
21 |
broken package, just an unconfigured one, so there's no harm to any |
22 |
users by them missing the config step. |
23 |
|
24 |
That and we hope that at some point in the future, portage will have a |
25 |
mechanism in place for logging all of the output for later. |
26 |
|
27 |
I wouldn't mind seeing some way to run all the config steps after the |
28 |
ebuilds, but in most cases you would only need to run the config step |
29 |
once, not on every upgrade of the package. |
30 |
|
31 |
> On 4/29/05, Chris Gianelloni <wolf31o2@g.o> wrote: |
32 |
> > On Fri, 2005-04-29 at 09:36 +0900, Jason Stubbs wrote: |
33 |
> > > > In fact, I've thought many times about supplying "pre-packages" that are |
34 |
> > > > no more than a collection of all the config files for a given package. |
35 |
> > > |
36 |
> > > What about the unused `ebuild [ebuild] config`? Isn't that the perfect place |
37 |
> > > for this sort of stuff? The only package that I know that uses this feature |
38 |
> > > is mysql. There are way more possibilities. |
39 |
> > |
40 |
> > I use it fairly regularly. I know that we use it on any game that |
41 |
> > requires a CD key, and also for VMWare (I bet most people don't know |
42 |
> > that!) to configure the modules. |
43 |
> > |
44 |
> > I hadn't considered using it for actually configuring a package (duh!) |
45 |
> > but that really is a very cool idea. Imagine if we started doing this |
46 |
> > for more packages. It would remove one of the primary complaints people |
47 |
> > have about Gentoo being "too hard" since they don't know "what to do |
48 |
> > next" after they emerge a package. If we got people used to "ebuild |
49 |
> > [ebuild] config", then we could remove a good bit of the issue. |
50 |
> > |
51 |
> > Just an idea, but one I'll probably be using more often now. |
52 |
> > |
53 |
> > -- |
54 |
> > Chris Gianelloni |
55 |
> > Release Engineering - Strategic Lead/QA Manager |
56 |
> > Games - Developer |
57 |
> > Gentoo Linux |
58 |
> > |
59 |
> > |
60 |
> > |
61 |
> |
62 |
-- |
63 |
Chris Gianelloni |
64 |
Release Engineering - Strategic Lead/QA Manager |
65 |
Games - Developer |
66 |
Gentoo Linux |