public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian <dol-sen@telus.net>
To: gentoo-portage-dev <gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] kernel drivers vs. portage
Date: Mon, 05 Jan 2004 22:41:41 -0800	[thread overview]
Message-ID: <1073371301.3689.11.camel@big_squirt.dol-sen.ca> (raw)
In-Reply-To: <1073237445.22251.13.camel@garath.local.domain>

On Sun, 2004-01-04 at 09:30, Paul Varner wrote:
> On Sun, 2004-01-04 at 09:17, Marius Mauch wrote:
> > On 01/04/04  Drake Wyrm wrote:
> > 
> > > What? No opinions, or everybody thinks I'm too much of an idiot to
> > > bother answering?
> > 
> > I think Daniel fixed that already by using the 'don't unmerge' feature
> > of CONFIG_PROTECT for /lib/modules.
> 
> It is fixed in the version of portage that is in CVS, but the fix still
> hasn't made it to the versions of portage that are marked stable.  In
> the CVS tree it was placed in version 1.345 of portage.py.  The version
> that is being distributed is currently 1.341 (See my comments at the end
> of bug #1477)
> 
> A manual work around that I have tested is to use env
> CONFIG_PROTECT="/lib/modules" when re-emerging packages such as
> alsa-driver for a new kernel.  However, I don't recommend placing it
> into the make.conf as typically you only want to protect the
> /lib/modules directory when doing the above.
> 
> I also would like portage-ng to handle kernel modules dependencies in a
> more automated fashion.  Someone commented that revdep-rebuild was a
> hack to get around some of the dependency shortcomings in the current
> version of portage.  The kernelmod-rebuild script that I recently wrote
> is also such a hack.
> 
> I didn't comment on the previous message as I didn't see anything that I
> disagreed with from a requirements perspective.
> 
> Regards,
> Paul
-- 
Thank you for working out this problem.  I, for a second thought I may
have instigated a change in portage for the better, but seeing the above
metioned bug I see it dates back much farther.   Even the fix has been
done for several months.

Again, thank you for the hard work to improve portage.

A side note:  Could changes, such as added features, or changed
functionality in core projects such as portage be announced in the GWN
as they make it to stable. (If it is not already normal)  It may be one
of the best ways for users to learn about such changes.

--
Brian <dol-sen@telus.net>


--
gentoo-portage-dev@gentoo.org mailing list


      reply	other threads:[~2004-01-06  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  7:16 [gentoo-portage-dev] multiple kernel driver emerges Brian
2004-01-02  7:31 ` Scott Taylor
2004-01-02 10:23   ` [gentoo-portage-dev] kernel drivers vs. portage Drake Wyrm
2004-01-04 12:50     ` Drake Wyrm
2004-01-04 15:17       ` Marius Mauch
2004-01-04 17:30         ` Paul Varner
2004-01-06  6:41           ` Brian [this message]

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=1073371301.3689.11.camel@big_squirt.dol-sen.ca \
    --to=dol-sen@telus.net \
    --cc=gentoo-portage-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