public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Federico Ferri <mescalinum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db
Date: Tue, 09 Dec 2008 23:35:18 +0100	[thread overview]
Message-ID: <493EF2A6.3000205@gentoo.org> (raw)
In-Reply-To: <20081209192124.GD2455@comet>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Donnie Berkholz wrote:
> On 01:44 Tue 09 Dec     , Federico Ferri wrote:
>> today I hit this annoyance, because my laptop hung in the middle
>> of an 'emerge -e @world' (checking that my world set compiles
>> with gcc-4.3... stopped at ~ 300 of 700  :S )
>>
>> I was looking for an entry in /var/db/pkg/<cat/pkg>/ that could
>> have told me the compiler used to build the package, but couldn't
>> find any. indeed it would be a fairly useful feature to have,
>> both for testing purposes, and for user's everyday maintenance.
>>
>> please criticize this with anything constructive you can think
>> of.
>
> 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

- --
Federico Ferri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk+8qQACgkQV/B5axfzrPs9BwCbBmbU3HVY0i6bqljlx3yZqICk
nT8AoJpgTbcNc/UOirCrPRw3zTOlxI5G
=uWSJ
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-12-09 22:35 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 [this message]
2008-12-10 19:13     ` Donnie Berkholz
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=493EF2A6.3000205@gentoo.org \
    --to=mescalinum@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