public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] module-rebuild
Date: Thu, 5 May 2005 17:33:16 +0200	[thread overview]
Message-ID: <20050505173316.05fe8e10@eusebe> (raw)
In-Reply-To: <1115192074.30481.15.camel@localhost>

On Wed, 04 May 2005 08:34:34 +0100
John Mylchreest <johnm@gentoo.org> wrote:

> I thought about this, but not wanting to depend on gentoolkit
> makes using equery for example a little awkward.
> This, I'm sure isn't fully feature-rich yet - and something
> like this will be the next addition to go in.
> 
> On Wed, 2005-05-04 at 15:24 +0900, Georgi Georgiev wrote:
> > 
> > I am not trying to shoot down your idea, but you could
> > probably use something similar to automatically generate the
> > list of packages to rebuild if the database is empty?
> > 

I've uploaded here the script i use here to rebuild my modules:
http://tdegreni.free.fr/gentoo/emodules

It's in bash too, and i think there are some functions that could
help for implementing the feature you are talking about:
 - get_kernel_KV() gives the $KV value corresponding to a kernel
sources tree.
 - get_cpv_KV() gives the $KV value from the saved environment of
an installed package.
 - list_cpv_to_build() gives the lists of packages providing
modules that were not last built using the right $KV.

It doesn't use equery neither, but rather direct access to the 
${ROOT}var/db/pkg.

Feel free to copy/past whatever you find useful (there's probably
no legal header, but it's gpl in my mind).

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


      reply	other threads:[~2005-05-05 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 23:00 [gentoo-dev] module-rebuild John Mylchreest
2005-05-04  4:15 ` Paul Varner
2005-05-04  6:24 ` Georgi Georgiev
2005-05-04  7:34   ` John Mylchreest
2005-05-05 15:33     ` Thomas de Grenier de Latour [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=20050505173316.05fe8e10@eusebe \
    --to=degrenier@easyconnect.fr \
    --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