From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db
Date: Wed, 10 Dec 2008 11:13:16 -0800 [thread overview]
Message-ID: <20081210191316.GA27879@comet> (raw)
In-Reply-To: <493EF2A6.3000205@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On 23:35 Tue 09 Dec , Federico Ferri wrote:
> Donnie Berkholz wrote:
> > As I mentioned on IRC, I think this isn't a very general use case
> > (given the existence of --resume, --keep-going, etc.) so code to
> > accomplish it
>
> the point was not resuming my emerge because the laptop hung. was more
> like: tracking which compiler built which package or vice-versa
>
> > would be better put into a custom portage bashrc than into portage
> > proper.
>
> yes, that makes sense. it could be an external tool, like
> revdep-rebuild is, which queries compiler by pkg, and eventually
> rebuilds packages (not) matching a certain compiler.
>
> but to accomplish this, an information about the compiler (in the pkg
> record) should be there. something like
> /var/db/pkg/<cat>/<pkg>/COMPILER
The point is solving the right problem in the right way. It seems like
you're starting with a solution you've picked and are working backward
to find a good use case & problem for it.
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-10 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 0:44 [gentoo-dev] Proposal: add a compiler-version entry to pkg db Federico Ferri
2008-12-09 1:39 ` Petteri Räty
2008-12-09 20:38 ` Federico Ferri
2008-12-09 6:07 ` Branko Badrljica
2008-12-09 18:55 ` Gordon Malm
2008-12-09 22:19 ` Federico Ferri
2008-12-09 19:21 ` Donnie Berkholz
2008-12-09 22:35 ` Federico Ferri
2008-12-10 19:13 ` Donnie Berkholz [this message]
2008-12-09 22:39 ` Marius Mauch
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=20081210191316.GA27879@comet \
--to=dberkholz@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