From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New global USE flag: logrotate
Date: Fri, 29 Apr 2005 11:32:08 -0400 [thread overview]
Message-ID: <1114788729.889.149.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <46059ce1050429062569aa89e4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2994 bytes --]
On Fri, 2005-04-29 at 09:25 -0400, Dan Meltzer wrote:
> The problem with ebuild config, at least until bug 11359 is handled,
> is if the package is emerged early on in a list of packages, there is
> a chance the person won't know to use ebuild config.... would it be
> possible for portage to run an ebuild config for _all_ packages that
> need it after _all_ packages that are being emerged are emerged? This
> way the upgrade goes without interference, but the customization waits
> until the person comes back, either that or an emerge config that
> tracks all packages that need config that have yet to be configged,
> currently, hoping a person thinks to ebuild packagename config is a
> lot to ask, unless every package takes use of it...
My opinion:
I really don't care.
We aren't doing anything in the config sections that cannot be done
manually, we're just making it easier by scripting it into a single
place. As more and more packages make use of the mechanism, people will
become used to using it. If someone doesn't use it, they won't have a
broken package, just an unconfigured one, so there's no harm to any
users by them missing the config step.
That and we hope that at some point in the future, portage will have a
mechanism in place for logging all of the output for later.
I wouldn't mind seeing some way to run all the config steps after the
ebuilds, but in most cases you would only need to run the config step
once, not on every upgrade of the package.
> On 4/29/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> > On Fri, 2005-04-29 at 09:36 +0900, Jason Stubbs wrote:
> > > > In fact, I've thought many times about supplying "pre-packages" that are
> > > > no more than a collection of all the config files for a given package.
> > >
> > > What about the unused `ebuild [ebuild] config`? Isn't that the perfect place
> > > for this sort of stuff? The only package that I know that uses this feature
> > > is mysql. There are way more possibilities.
> >
> > I use it fairly regularly. I know that we use it on any game that
> > requires a CD key, and also for VMWare (I bet most people don't know
> > that!) to configure the modules.
> >
> > I hadn't considered using it for actually configuring a package (duh!)
> > but that really is a very cool idea. Imagine if we started doing this
> > for more packages. It would remove one of the primary complaints people
> > have about Gentoo being "too hard" since they don't know "what to do
> > next" after they emerge a package. If we got people used to "ebuild
> > [ebuild] config", then we could remove a good bit of the issue.
> >
> > Just an idea, but one I'll probably be using more often now.
> >
> > --
> > Chris Gianelloni
> > Release Engineering - Strategic Lead/QA Manager
> > Games - Developer
> > Gentoo Linux
> >
> >
> >
>
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-29 15:32 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 8:30 [gentoo-dev] New global USE flag: logrotate Henrik Brix Andersen
2005-04-28 8:51 ` Robin H. Johnson
2005-04-28 10:34 ` Henrik Brix Andersen
2005-04-28 10:44 ` Robin H. Johnson
2005-04-28 11:01 ` Thomas de Grenier de Latour
2005-04-28 11:01 ` Henrik Brix Andersen
2005-04-28 14:00 ` Mike Frysinger
2005-04-28 14:08 ` Thomas de Grenier de Latour
2005-04-28 12:05 ` Ciaran McCreesh
2005-04-28 12:56 ` Georgi Georgiev
2005-04-28 13:41 ` Cory Visi
2005-04-28 13:44 ` Lance Albertson
2005-04-28 13:47 ` Ciaran McCreesh
2005-04-28 15:23 ` Chris Gianelloni
2005-04-28 15:51 ` Thomas de Grenier de Latour
2005-04-28 19:48 ` Donnie Berkholz
2005-04-28 20:16 ` Ciaran McCreesh
2005-04-28 20:21 ` Donnie Berkholz
2005-04-28 22:18 ` Grant Goodyear
2005-04-28 22:28 ` Donnie Berkholz
2005-04-29 0:36 ` Jason Stubbs
2005-04-29 0:43 ` Donnie Berkholz
2005-04-29 12:26 ` Chris Gianelloni
2005-04-29 13:25 ` Dan Meltzer
2005-04-29 13:55 ` Jason Stubbs
2005-04-29 15:52 ` Chris Gianelloni
2005-04-29 16:17 ` Jason Stubbs
2005-04-29 17:26 ` Chris Gianelloni
2005-04-29 17:25 ` Jason Stubbs
2005-04-29 17:46 ` Chris Gianelloni
2005-04-29 18:03 ` Jason Stubbs
2005-04-29 15:32 ` Chris Gianelloni [this message]
2005-04-29 17:44 ` Robin H. Johnson
2005-04-29 18:06 ` Jason Stubbs
2005-04-29 18:59 ` Chris Gianelloni
2005-04-29 19:17 ` Donnie Berkholz
2005-04-29 9:32 ` Christian Birchinger
2005-04-28 22:32 ` Tom Wesley
2005-04-28 23:10 ` Spider
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 9:22 Tom Martin
2005-08-02 10:44 ` Anthony Gorecki
2005-08-02 12:17 ` Chris Gianelloni
2005-08-02 17:04 ` Tom Martin
2005-08-02 17:24 ` Chris Gianelloni
2005-08-02 12:34 ` tomk
2005-08-02 16:48 ` Donnie Berkholz
2005-08-02 17:01 ` Alec Warner
2005-08-02 17:33 ` Ciaran McCreesh
2005-08-02 17:48 ` Alec Joseph Warner
2005-08-02 17:59 ` Ciaran McCreesh
2005-08-02 17:52 ` Donnie Berkholz
2005-08-02 18:12 ` Ciaran McCreesh
2005-08-02 17:58 ` Alin Nastac
2005-08-03 23:50 ` Tom Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114788729.889.149.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox