[gentoo-dev] Proposal: add a compiler-version entry to pkg db

[gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Federico Ferri]

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

Hello,
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.

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

iEYEARECAAYFAkk9v14ACgkQV/B5axfzrPucugCfRN51KpJZ/HYCYA3v/Z2lAhaf
8eUAniZONnbWtN4f5CblJzaxEMbFWI3m
=4l7H
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

Federico Ferri wrote:
> Hello,
> 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 )
> 

Consider using emerge --keep-going next time.

> 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.
> 

But the idea isn't that bad imfo. Maybe save the output of emerge --info
in general and it could be easily made available for bug filing. If it
was a while since you emerged the package your emerge --info could now
be different from the merge time and now for example reflect your use flags.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Federico Ferri]

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

Petteri Räty wrote:
> Federico Ferri wrote:
>> Hello,
>> 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 )
>>
>
> Consider using emerge --keep-going next time.
>
>> 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.
>>
>
> But the idea isn't that bad imfo. Maybe save the output of emerge --info
> in general and it could be easily made available for bug filing. If it
> was a while since you emerged the package your emerge --info could now
> be different from the merge time and now for example reflect your use
flags.
nice point!
I didn't see the whole potential of my proposal :-D

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

iEYEARECAAYFAkk+11kACgkQV/B5axfzrPvq4QCgvs5zVMieQADGfdq8DcJZSNzK
+3QAoKmH/TzzJ/9ZmqgWrXK5C9jINsI3
=/qv2
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Branko Badrljica]

While at it, it might be useful to have someghing like compiler-use file 
( like package.use) for per-package compiler version and FLAGS to be used.

It is annoying to have emerge -eD world fail because some package 
requires specific compiler version or because gcc-3.4 can't be compiled 
with -march=barcelona or with -combine CFLAGS...
There should also be an option for the user to match compiler with 
compiler version, used to compile some other package. Perhaps with 
naming full name of the package instead of compiler name and version 
string in some file, like /etc/portage/package-infra.use or something 
like that.

That approach could also be used for selecting specific version of 
perl/python/ruby/autotools/whatnot.








ederico Ferri wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
> 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.
>
> thanks
> - --
> Federico Ferri
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkk9v14ACgkQV/B5axfzrPucugCfRN51KpJZ/HYCYA3v/Z2lAhaf
> 8eUAniZONnbWtN4f5CblJzaxEMbFWI3m
> =4l7H
> -----END PGP SIGNATURE-----
>
>
>
>
>   

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Gordon Malm]

Should be able to find which gcc was used by checking LDPATH in the 
environment.bz2.  I believe it is about the only gcc version information 
recorded in /var/db/pkg/<category>/<package>/ though.

Gordon Malm (gengor)

On Monday, December 8, 2008 16:44:16 Federico Ferri wrote:
> Hello,
> 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.
>
> thanks

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Federico Ferri]

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

Gordon Malm wrote:
> Should be able to find which gcc was used by checking LDPATH in the
>  environment.bz2.  I believe it is about the only gcc version
> information recorded in /var/db/pkg/<category>/<package>/ though.
>
$ find /var/db/pkg -name environment.bz2 | wc
- -l                        
747
$ find /var/db/pkg -name environment.bz2 -exec bzgrep -q LDPATH '{}'
';' -print | wc -l
11

sorry, that appears to be of little help

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

iEYEARECAAYFAkk+7uUACgkQV/B5axfzrPsaJwCdFVpGO3fYAMcyhRTN2QdRuZkH
2CsAniO7oZCxZSC6lt/j/+PRmrgyCyuI
=5mFz
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

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 
would be better put into a custom portage bashrc than into portage 
proper.

ISTR that you could no longer resume for some reason. Perhaps what you 
really wanted was a way to save the resume list across multiple emerges?

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Federico Ferri]

-----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-----

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Donnie Berkholz]

[-- 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 --]

Re: [gentoo-dev] Proposal: add a compiler-version entry to pkg db

[Marius Mauch]

On Tue, 9 Dec 2008 11:21:24 -0800
Donnie Berkholz <dberkholz@gentoo.org> 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 would be better put into a custom portage bashrc than
> into portage proper.
> 
> ISTR that you could no longer resume for some reason. Perhaps what
> you really wanted was a way to save the resume list across multiple
> emerges?

For the given use case it might also be an option to use the AgeSet
handler in portage-2.2, e.g.
   emerge -p '@old{class=dbapi.AgeSet,age=2}'
to list all installed packages that have been installed more than two
days ago.

Marius