Re: [gentoo-dev] Gentoo's plan to remove .la files: eutils function

2010-10-31 Thread Christopher Schwan
Hi,

I followed this discussion quietly until now - I wonder why no one (?) has 
mentioned the autotool-utils.eclass which is dedicated for this purpose (la-
file removal, static-libs USE-flag, etc), I think. This eclass also provides a 
function remove_libtool_files which does what delete_libtool_archives would 
do, but it also checks for situation where the files would be needed.

On Sunday 31 October 2010 05:28:42 Jorge Manuel B. S. Vicetto wrote:
 Hi.
 
 As outlined in the global email about this issue, this email is to start
 a thread about the eutils function. Please reply to this thread if you
 have any comments about this point.
 
 1. Add a function to eutils to deal with the removal of the .la files.
 
 delete_libtool_archives() { find ${@:$D} -name '*.la' -delete }
 
 That function was suggested by Diego, but Arfrever has argued that we
 should replace : with - as '${@:$D} expands to a subarray containing
 elements starting with element with index $D (where element 0 is $0)'.
 The point in having this function in eutils is to ensure we use a
 consistent way to address the .la files. This will also make it much
 easier to adapt or review this function if needed.

Cheers,

Christopher



Re: [gentoo-dev] Gentoo's plan to remove .la files

2010-10-31 Thread Pacho Ramos
El dom, 31-10-2010 a las 03:25 -0100, Jorge Manuel B. S. Vicetto
escribió:
 3. Add a page to the QA project space (unless they're not interested)
 about la files and how to deal with them
 
 I think we can ask Diego to use large parts of his blog posts and charts
 about .la files[1], [2], [3], [4] as a source for the document. We can
 also add some basic info from the autobook[5], [6]. The goal would be to
 have a document similar to our own --as-needed guide [7] and to other
 distributions[8], [9].
 Anyone wishes to volunteer for this task?
 QA would such a document be welcomed in your project space?

Hello

I rely a lot on devmanual, then, I think would be interesting to create
a section on it telling us when should we remove .la files and how to do
it properly.

Thanks a lot :-)


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] Gentoo's plan to remove .la files: QA document

2010-10-31 Thread Pacho Ramos
El dom, 31-10-2010 a las 03:32 -0100, Jorge Manuel B. S. Vicetto
escribió:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi.
 
 As outlined in the global email about this issue, this email is to start
 a thread about the QA document. Please reply to this thread if you
 have any comments about this point.
 
 
 3. Add a page to the QA project space (unless they're not interested)
 about la files and how to deal with them
 
 I think we can ask Diego to use large parts of his blog posts and charts
 about .la files[1], [2], [3], [4] as a source for the document. We can
 also add some basic info from the autobook[5], [6]. The goal would be to
 have a document similar to our own --as-needed guide [7] and to other
 distributions[8], [9].
 Anyone wishes to volunteer for this task?
 QA would such a document be welcomed in your project space?
 
 
  [1] - http://blog.flameeyes.eu/2008/04/14/whatabout-those-la-files
  [2] -
 http://blog.flameeyes.eu/2008/07/02/again-about-la-files-or-why-should-they-be-killed-off-sooner-rather-than-later
  [3] -
 http://blog.flameeyes.eu/2009/07/06/identifying-pointless-la-files-for-plugins
  [4] -
 http://blog.flameeyes.eu/2009/09/28/removing-la-files-for-dum-w-uncertain-people
  [5] - http://sources.redhat.com/autobook/autobook/autobook_11.html#SEC11
  [6] - http://sources.redhat.com/autobook/autobook/autobook_68.html#SEC68
  [7] - http://www.gentoo.org/proj/en/qa/asneeded.xml
  [8] - http://wiki.mandriva.com/en/Libtool_archives#shared_build
  [9] - http://wiki.mandriva.com/en/Overlinking
 
 
 - -- 
 Regards,

I rely a lot on devmanual, then, I think would be interesting to create
a section on it telling us when should we remove .la files and how to do
it properly.

Thanks a lot :-)


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] Changes in server profiles

2010-10-31 Thread Markos Chandras
On Sat, Oct 30, 2010 at 10:59:08PM -0400, Richard Freeman wrote:
 On 10/30/2010 08:10 AM, Thomas Sachau wrote:
  If i remember it right, the server profile was created for those people, 
  who only want a minimum
  amount of default profile enabled USE flags (so no desktop profile because 
  of that), but on the
  other side dont want to do the additional work/checks/reading for hardened 
  profiles (which have much
  less profile enabled USE flags, but also have the special gcc, glibc and 
  Kernel), basicly a profile,
  which does the same as hardened profile without the specific hardened bits.
  
  
 
 Isn't this essentially what the default profile is?  Basically server is
 just default + USE=apache2 ldap mysql snmp truetype xml.
Well it shouldn't be like that. And if the default profile is pretty
much the same as the server one, then please consider removing the
server profile as it makes no sense then
 

-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411  3477 F7F7 1E8E 441A C410


pgpXa9NxXTorT.pgp
Description: PGP signature


Re: [gentoo-dev] Gentoo's plan to remove .la files: eutils function

2010-10-31 Thread Thomas Sachau
Am 31.10.2010 09:28, schrieb Christopher Schwan:
 Hi,
 
 I followed this discussion quietly until now - I wonder why no one (?) has 
 mentioned the autotool-utils.eclass which is dedicated for this purpose (la-
 file removal, static-libs USE-flag, etc), I think. This eclass also provides 
 a 
 function remove_libtool_files which does what delete_libtool_archives 
 would 
 do, but it also checks for situation where the files would be needed.
 
 On Sunday 31 October 2010 05:28:42 Jorge Manuel B. S. Vicetto wrote:
 Hi.

 As outlined in the global email about this issue, this email is to start
 a thread about the eutils function. Please reply to this thread if you
 have any comments about this point.

 1. Add a function to eutils to deal with the removal of the .la files.

 delete_libtool_archives() { find ${@:$D} -name '*.la' -delete }

 That function was suggested by Diego, but Arfrever has argued that we
 should replace : with - as '${@:$D} expands to a subarray containing
 elements starting with element with index $D (where element 0 is $0)'.
 The point in having this function in eutils is to ensure we use a
 consistent way to address the .la files. This will also make it much
 easier to adapt or review this function if needed.
 
 Cheers,
 
 Christopher
 
 

Please dont top post, it makes it harder to read threads.

That suggested line will remove all .la files blindly, but there are 2 types of 
.la files:
-those, which are only used for linking/static files
-those, which are used at runtime, e.g. for plugins

The line should exclude those .la files, which contain shouldnotlinkto=yes or 
directly use the
autotools-utils eclass as suggested, since it already contains this 
functionality together with a
nice USE flag (static-libs) for it.


-- 
Thomas Sachau

Gentoo Linux Developer



signature.asc
Description: OpenPGP digital signature


[gentoo-dev] Re: Gentoo's plan to remove .la files: eutils function

2010-10-31 Thread Diego Elio Pettenò
Il giorno dom, 31/10/2010 alle 13.26 +0100, Thomas Sachau ha scritto:
 
 
 The line should exclude those .la files, which contain
 shouldnotlinkto=yes or directly use the
 autotools-utils eclass as suggested, since it already contains this
 functionality together with a
 nice USE flag (static-libs) for it. 

This would exclude all plugin .la files which are also NOT NEEDED in
most cases.

And I'm starting to get angry at people who install .la files for PAM
modules… or Ruby extensions… or Python modules… and so on so…

_Most of them must die on a package-by-package basis._

-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/



signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Diego Elio Pettenò
Il giorno dom, 31/10/2010 alle 03.30 -0100, Jorge Manuel B. S. Vicetto
ha scritto:
 As agreed in the meeting, as a first draft, we have that the motion
 is
 to drop la files, when appropriate, through the use of a function in
 eutils that will only be called if the static-libs use flag is not set
 or unless the package relies on pkg-config. 

Let's differentiate already:

For *plugin* .la files, they should removed if the software is not
relying on them to load its plugins, see [1]. This is the case for PAM,
Python, Ruby and I guess Perl, which commonly receive stupid .la files
in their paths. Repeat after me: they should just all be deleted _right
now_ since they are not going to be linked by anyone else and thus
Portage 2.1.9 is not making any difference.

For *libraries* .la files, they should removed if:

 - you are not building any static archive at all (and this should
happen almost every time the library provides a plugin interface as the
plugins wouldn't work with a statically-linked archive);
 - the official way to link to the library is pkg-config or some other
-config package;
 - the package started as, or is evolving into, a non-autotools-based
package (most of X11 falls into this line since they started with imake
and that one never produced .la files so nobody should be relying on
them);
 - the library depends on no other library at all (so there are no
dependencies to cater);
 - finally, if USE=static-libs is set

Do note that static-libs USE flag causing the removal is the _least_
common case, quite very likely, you're going to stop at the second line
in my list and then delete the files. It's similar to what I wrote on
[2], by the way.


[1]
http://blog.flameeyes.eu/2009/07/06/identifying-pointless-la-files-for-plugins
[2]
http://blog.flameeyes.eu/2009/09/28/removing-la-files-for-dum-w-uncertain-people
-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/





Re: [gentoo-dev] Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Pacho Ramos
El dom, 31-10-2010 a las 14:56 +0100, Diego Elio Pettenò escribió:
 Il giorno dom, 31/10/2010 alle 03.30 -0100, Jorge Manuel B. S. Vicetto
 ha scritto:
  As agreed in the meeting, as a first draft, we have that the motion
  is
  to drop la files, when appropriate, through the use of a function in
  eutils that will only be called if the static-libs use flag is not set
  or unless the package relies on pkg-config. 
 
 Let's differentiate already:
 
 For *plugin* .la files, they should removed if the software is not
 relying on them to load its plugins, see [1]. This is the case for PAM,
 Python, Ruby and I guess Perl, which commonly receive stupid .la files
 in their paths. Repeat after me: they should just all be deleted _right
 now_ since they are not going to be linked by anyone else and thus
 Portage 2.1.9 is not making any difference.
 

In that case, I think the work on these cases should start as soon as
possible, but I think that getting bugs reported (probably from your
next tinderbox run if possible) would help. For example, I have just
seen in my system that packages like dev-python/pyorbit and
dev-libs/libgamin are installing these .la files that should not be
needed, but I am sure lots of other python packages are also
affected :-/.

But I would also like to know what would be the best way to drop them in
these cases:
- For python, looks like calling python_clean_installation_image from
python.eclass at src_install phase is the proper way.
- For pam, ruby or perl I have no idea :-(

Thanks


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] Changes in server profiles

2010-10-31 Thread Alex Alexander
On Sun, Oct 31, 2010 at 11:50:02AM +, Markos Chandras wrote:
 On Sat, Oct 30, 2010 at 10:59:08PM -0400, Richard Freeman wrote:
  On 10/30/2010 08:10 AM, Thomas Sachau wrote:
   If i remember it right, the server profile was created for those people, 
   who only want a minimum
   amount of default profile enabled USE flags (so no desktop profile 
   because of that), but on the
   other side dont want to do the additional work/checks/reading for 
   hardened profiles (which have much
   less profile enabled USE flags, but also have the special gcc, glibc and 
   Kernel), basicly a profile,
   which does the same as hardened profile without the specific hardened 
   bits.
   
   
  
  Isn't this essentially what the default profile is?  Basically server is
  just default + USE=apache2 ldap mysql snmp truetype xml.
 Well it shouldn't be like that. And if the default profile is pretty
 much the same as the server one, then please consider removing the
 server profile as it makes no sense then

Please don't. The fact that there are only a few changes doesn't make it
useless. Also, you'd be forcing all users currently using the profile to
migrate without any real reason.

-- 
Alex Alexander | wired
Gentoo Linux Developer | Council / Qt / Chromium / more
www.linuxized.com


pgp22L3Od8mYh.pgp
Description: PGP signature


Re: [gentoo-dev] Changes in server profiles

2010-10-31 Thread Markos Chandras
On Sun, Oct 31, 2010 at 04:38:09PM +0200, Alex Alexander wrote:
 On Sun, Oct 31, 2010 at 11:50:02AM +, Markos Chandras wrote:
  On Sat, Oct 30, 2010 at 10:59:08PM -0400, Richard Freeman wrote:
   On 10/30/2010 08:10 AM, Thomas Sachau wrote:
If i remember it right, the server profile was created for those 
people, who only want a minimum
amount of default profile enabled USE flags (so no desktop profile 
because of that), but on the
other side dont want to do the additional work/checks/reading for 
hardened profiles (which have much
less profile enabled USE flags, but also have the special gcc, glibc 
and Kernel), basicly a profile,
which does the same as hardened profile without the specific hardened 
bits.


   
   Isn't this essentially what the default profile is?  Basically server is
   just default + USE=apache2 ldap mysql snmp truetype xml.
  Well it shouldn't be like that. And if the default profile is pretty
  much the same as the server one, then please consider removing the
  server profile as it makes no sense then
 
 Please don't. The fact that there are only a few changes doesn't make it
 useless. Also, you'd be forcing all users currently using the profile to
 migrate without any real reason.
 
 -- 
 Alex Alexander | wired
 Gentoo Linux Developer | Council / Qt / Chromium / more
 www.linuxized.com

You are missing the point here. My intention is to make server profiles
more generic for server usage and not optimised for ldap/web hosting
services


-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411  3477 F7F7 1E8E 441A C410


pgpg7iqQO6kPd.pgp
Description: PGP signature


[gentoo-dev] Re: Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Diego Elio Pettenò
Il giorno dom, 31/10/2010 alle 15.31 +0100, Pacho Ramos ha scritto:
 In that case, I think the work on these cases should start as soon as
 possible,

I have said that before.

 but I think that getting bugs reported (probably from your
 next tinderbox run if possible) would help.

Search for pointless .la and you'll find a bunch of reported bugs; I
stopped mostly because of GNOME-related packages (which where the main
cause of the bugs):

 - Tester refused fixing telepathy and the like altogether stating that
it's an upstream issue;
 - leio stated that he didn't care about removing those that are simply
pointless already because he wanted to do it in one big sweep, and the
bugs I would report would just linger there indefinitely.

  For example, I have just
 seen in my system that packages like dev-python/pyorbit and
 dev-libs/libgamin are installing these .la files that should not be
 needed, but I am sure lots of other python packages are also
 affected :-/.

dev-libs/libbeagle (maintainer-needed)
sys-auth/fprintd (xmw)
dev-python/pygoocanvas (gnome/python)
x11-libs/xpyb (x11)
media-libs/hamlib (tomjbe)
net-libs/gtk-vnc (gnome)
dev-python/pyclutter-gtk (gnome)
dev-python/pyclutter (gnome)
media-libs/pdflib (maintainer-needed)
dev-libs/libnatspec (invalid metadata?)
dev-python/notify-python (dev-zero/python)
dev-python/telepathy-farsight (nirbheek/tester/voip)
sci-libs/geos (sci-geosciences/postgres)
sys-libs/libieee1284 (base-system)
app-i18n/libtomoe-gtk (cjk)
app-i18n/tomoe (cjk)
net-libs/farsight2 (voip)
x11-libs/vte (gnome)
dev-python/pyorbit (gnome)
gnome-extra/libgsf (gnome)
dev-python/pygtksourceview (gnome)
gnome-base/gnome-keyring (gnome)
dev-libs/libxslt (gnome)

And this is just a list I produced out of the current logs I have on the
tinderbox (64-bit version) for the paths of the plugins I _know_ are not
loaded through .la files… I think there are a few hundreds .la files in
packages maintained by gnome alone that are not being used at all and
could have been removed years ago (reducing the pressure of
revdep-rebuild on broken .la files).

 - For pam, ruby or perl I have no idea :-(

find $(get_pammoddir) -name '*.la' -delete
find /usr/$(get_libdir)/ruby -name '*.la' -delete

Nothing fancy, just delete them ;)

-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/



signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Re: [gentoo-dev-announce] Gentoo's plan to remove .la files

2010-10-31 Thread Denis Dupeyron
On Sat, Oct 30, 2010 at 10:25 PM, Jorge Manuel B. S. Vicetto
jmbsvice...@gentoo.org wrote:
 As decided in the last council's meeting, following the recent
 discussions about .la files removal, I'm sending an email to this list
 with a proposal for a plan to address this issue.

1- Why is a proposal sent to gentoo-dev-announce? Shouldn't that
rather be worked out before being announced? Or is there some context
that the ordinary user or developer is missing?

2- Sending to both gentoo-dev and gentoo-council makes sure that this
splits into twice as many threads as it would have. Good luck with
merging them after that.

Denis.



Re: [gentoo-dev] Re: Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Thomas Beierlein
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, 31 Oct 2010 15:52:51 +0100
Diego Elio Pettenò flamee...@gmail.com wrote:

   For example, I have just
  seen in my system that packages like dev-python/pyorbit and
  dev-libs/libgamin are installing these .la files that should not be
  needed, but I am sure lots of other python packages are also
  affected :-/.
 
snip..
 media-libs/hamlib (tomjbe)
snip..

Above package provides around 38 .la files. I am not quite sure yet
about hamlibtcl.la, libhamlib++.la, libhamlib.la and _Hamlib.la. Maybe
they can go -- will look into that in next days.

But the other ones are plugins (or backends in hamlib terms) which get
loaded via libltdl according to the radio tranceiver family in question.

See as an example the following strace for calling the simple frontend
(rigctl) for the Kenwood TS-570 tranceiver (Model 204).

strace -e open rigctl -m 204
open(/etc/ld.so.cache, O_RDONLY)  = 3
open(/usr/lib64/hamlib/libhamlib.so.2, O_RDONLY) = 3
open(/lib/libpthread.so.0, O_RDONLY)  = 3
open(/lib/libc.so.6, O_RDONLY)= 3
open(/usr/lib/libltdl.so.7, O_RDONLY) = 3
open(/lib/libm.so.6, O_RDONLY)= 3
open(/lib/libusb-0.1.so.4, O_RDONLY)  = 3
open(/lib/libdl.so.2, O_RDONLY)   = 3
open(/usr/lib64/hamlib/hamlib-kenwood.la, O_RDONLY) = 3
open(/usr/lib64/hamlib/hamlib-kenwood.so, O_RDONLY) = 3
open(/dev/ttyS0, O_RDWR|O_NOCTTY|O_NONBLOCK) = 3


If I read the discussion correctly we will still need to keep these .la
files around.

Regards,
Thomas.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAkzNvuQACgkQQe4uqXYgU9XQOACfdh6Y0K4tEaNfxZWuLQ4IKY9z
COcAniZAbl1YcvRLrGQE6k2Jph2jNOkN
=u989
-END PGP SIGNATURE-


[gentoo-dev] Re: Re: Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Diego Elio Pettenò
Il giorno dom, 31/10/2010 alle 20.09 +0100, Thomas Beierlein ha scritto:
 
 If I read the discussion correctly we will still need to keep
 these .la
 files around.
 
Most likely, yes… you can go a bit deeper about them (for instance
PulseAudio can load its plugins with libltdl even if the .la files are
not around, and the author _always_ recommended removing them), but
that's probably something we don't have to care about so much as it is.

For what concerns the list I provided, that's just the output of the
tinderbox in the case of hamlib, it was _Hamlib.la that triggered it, it
is installed in the Python tree and Python does not use .la files.

-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/





Re: [gentoo-dev] Changes in server profiles

2010-10-31 Thread Alec Warner
On Sun, Oct 31, 2010 at 7:38 AM, Alex Alexander wi...@gentoo.org wrote:
 On Sun, Oct 31, 2010 at 11:50:02AM +, Markos Chandras wrote:
 On Sat, Oct 30, 2010 at 10:59:08PM -0400, Richard Freeman wrote:
  On 10/30/2010 08:10 AM, Thomas Sachau wrote:
   If i remember it right, the server profile was created for those people, 
   who only want a minimum
   amount of default profile enabled USE flags (so no desktop profile 
   because of that), but on the
   other side dont want to do the additional work/checks/reading for 
   hardened profiles (which have much
   less profile enabled USE flags, but also have the special gcc, glibc and 
   Kernel), basicly a profile,
   which does the same as hardened profile without the specific hardened 
   bits.
  
  
 
  Isn't this essentially what the default profile is?  Basically server is
  just default + USE=apache2 ldap mysql snmp truetype xml.
 Well it shouldn't be like that. And if the default profile is pretty
 much the same as the server one, then please consider removing the
 server profile as it makes no sense then

 Please don't. The fact that there are only a few changes doesn't make it
 useless. Also, you'd be forcing all users currently using the profile to
 migrate without any real reason.

We don't really delete profiles (maybe once every few years...)  We
could opt to mark the server target deprecated and not update it
anymore.

-A


 --
 Alex Alexander | wired
 Gentoo Linux Developer | Council / Qt / Chromium / more
 www.linuxized.com




Re: [gentoo-dev] Changes in server profiles

2010-10-31 Thread Markos Chandras
On Sun, Oct 31, 2010 at 12:47:32PM -0700, Alec Warner wrote:
 On Sun, Oct 31, 2010 at 7:38 AM, Alex Alexander wi...@gentoo.org wrote:
  On Sun, Oct 31, 2010 at 11:50:02AM +, Markos Chandras wrote:
  On Sat, Oct 30, 2010 at 10:59:08PM -0400, Richard Freeman wrote:
   On 10/30/2010 08:10 AM, Thomas Sachau wrote:
If i remember it right, the server profile was created for those 
people, who only want a minimum
amount of default profile enabled USE flags (so no desktop profile 
because of that), but on the
other side dont want to do the additional work/checks/reading for 
hardened profiles (which have much
less profile enabled USE flags, but also have the special gcc, glibc 
and Kernel), basicly a profile,
which does the same as hardened profile without the specific hardened 
bits.
   
   
  
   Isn't this essentially what the default profile is?  Basically server is
   just default + USE=apache2 ldap mysql snmp truetype xml.
  Well it shouldn't be like that. And if the default profile is pretty
  much the same as the server one, then please consider removing the
  server profile as it makes no sense then
 
  Please don't. The fact that there are only a few changes doesn't make it
  useless. Also, you'd be forcing all users currently using the profile to
  migrate without any real reason.
 
 We don't really delete profiles (maybe once every few years...)  We
 could opt to mark the server target deprecated and not update it
 anymore.
 
 -A
 
 
  --
  Alex Alexander | wired
  Gentoo Linux Developer | Council / Qt / Chromium / more
  www.linuxized.com
 
 
I did not literally mean what I said. My intention is to make server
profiles useful. They are not equivalent to default profile ( at least they
shouldn't). I see that this discussion is moving to dead-end so I will
to what I suggested at least at the amd64 profile

1) drop apache2, ldap use flags
2) Adjust warning message to reflect reallity

in 72 hours

---
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411  3477 F7F7 1E8E 441A C410


pgprKQlvC9w8x.pgp
Description: PGP signature


Re: [gentoo-dev] Re: Re: Re: Gentoo's plan to remove .la files: wording about when and how to drop .la files

2010-10-31 Thread Thomas Beierlein
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, 31 Oct 2010 20:15:17 +0100
Diego Elio Pettenò flamee...@gmail.com wrote:

 Il giorno dom, 31/10/2010 alle 20.09 +0100, Thomas Beierlein ha
 scritto:
  
  If I read the discussion correctly we will still need to keep
  these .la
  files around.
  
 Most likely, yes… you can go a bit deeper about them (for instance
 PulseAudio can load its plugins with libltdl even if the .la files are
 not around, and the author _always_ recommended removing them), but
 that's probably something we don't have to care about so much as it
 is.
 
Anyway, I will look into it and try it out.

 For what concerns the list I provided, that's just the output of the
 tinderbox in the case of hamlib, it was _Hamlib.la that triggered it,
 it is installed in the Python tree and Python does not use .la files.
 
Ok. Thnaks for the info. Another one will be libhamlib.la as it works
with pkg-config - so no need for it.

Regards,

Thomas.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAkzN3JcACgkQQe4uqXYgU9WejwCdFbv1YtXLgunYF0FVXyZWJUmA
2igAn2XloPLjVitP0n0Sh3f9oDi3LOue
=asZZ
-END PGP SIGNATURE-


Re: [gentoo-dev] Re: [gentoo-dev-announce] Gentoo's plan to remove .la files

2010-10-31 Thread Jorge Manuel B. S. Vicetto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 31-10-2010 15:31, Denis Dupeyron wrote:
 On Sat, Oct 30, 2010 at 10:25 PM, Jorge Manuel B. S. Vicetto
 jmbsvice...@gentoo.org wrote:
 As decided in the last council's meeting, following the recent
 discussions about .la files removal, I'm sending an email to this list
 with a proposal for a plan to address this issue.
 
 1- Why is a proposal sent to gentoo-dev-announce? Shouldn't that
 rather be worked out before being announced? Or is there some context
 that the ordinary user or developer is missing?

I sent this purposely to gentoo-dev-announce as this is an important
subject and I wanted to give interested parties a chance to be aware of
the discussion and to be able to provide input.

 2- Sending to both gentoo-dev and gentoo-council makes sure that this
 splits into twice as many threads as it would have. Good luck with
 merging them after that.

I CC'ed the council alias so all of the council members would get the
original email starting the discussion about this proposal.

 Denis.
 

- -- 
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMzee3AAoJEC8ZTXQF1qEPHHYP/1rg93mdCLcHdbrmktZ73v+u
gQcQxu6hffBLmdstQxO+XkU3hdKt+nwxBIoSGje9yfkwxxxu2zrlkrMBIgv9yKlu
sjYUvmgHVBbpZS/qwiFqEXhUhWbkm49X67Ei6Iy5jSWHRhHOiJ56+TfTgIAbRlEv
RCWAcF+KpfGnDwR/L+vDnZPxXURmTVqzh5sDm25vCpsUVUYS+5y7tQxia4Z4Lz9P
gVzLdvJQSiDZOxLIA7CUGzAHIYbHZjQ4bEBjNECSXjKZSH15fbK+0TxJ7/aBYZph
ZLVzawGIjoozdgoN8zfZP0BdL12TRTyFEAxuGDJAEwq+238QNt+f5a22VNLTqStl
1opWaJHJdye8z+PHyaGB1I7FaF+nw1VqFevw7w4MWBx2s0RYA9UNubLPMIg82fY4
i9tIvKl6DyjBd/w/0ApAreL42ZDifGDPdneX1yM77qLtavy4DUbxsGpPUZc9x8rx
p7dMlzakDj78YPmvhPCTCq2ZzJPEEgeF+TbhOsnWDRj3OxDiQIA0GrFHqxk7X8nk
cOhmFoJMi/uOVCqHxSWfxFF8wQYh0znN8kyD8Xe/6wxEGiZIGDeKkEl4X4zHJg1P
m8ZvJzA/j7UKDbXtr3fGj1crdfC1xLxLU/Lz7v/0rqSg11SNgsAfSAdlq5PcQ09D
Em7TYvtIUjkb4nq2N5Rm
=dwIq
-END PGP SIGNATURE-



[gentoo-dev] RFC: mesa.eselect

2010-10-31 Thread Chí-Thanh Christopher Nguyễn

Hi,

media-libs/mesa-7.9 has been sitting in the X11 overlay for some time 
and the X11 team are planning to move it to portage soon.
The new release brings a number of improvements, including much better 
Gallium3D support. One feature that we would like to add to Mesa in 
Gentoo is the ability to switch between classic and gallium drivers 
via an eselect module.


Attached you will find the eselect module which we used in the X11 
overlay, and the configuration file from mesa. There are still some 
things on the TODO list but I consider them not blockers for addition to 
the tree. As this is the first eselect module I have written, I would 
welcome your comments and pointers.


TODO:
 * Add support for switching emul-linux-x86-opengl on amd64 multilib
 * Accept numbers as do_set() arguments
 * Make the code a bit more compact
Untested:
 * Prefix support


Best regards,
Chí-Thanh Christopher Nguyễn

# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id: $  

DESCRIPTION=Manage the OpenGL driver architecture used by media-libs/mesa
MAINTAINER=x...@gentoo.org
SVN_DATE='$Date: $'
VERSION=$(svn_date_to_version ${SVN_DATE} )
EBUILD_VERSION=0.0.7

CONFIG_DIR=${EROOT}/usr/share/mesa
MESA_DIR=${EROOT}/usr/lib/mesa
DRI_DIR=${EROOT}/usr/lib/dri

source ${CONFIG_DIR}/eselect-mesa.conf || die Failed to source config

# receives a filename of the driver as argument, outputs the architecture 
(classic or gallium)
drivername_to_architecture() {
local drivername=$1
local x
local y
local z
for x in ${MESA_IMPLEMENTATIONS}; do
for y in classic gallium; do
z=$(get_drivername ${x} ${y})
if [[ ${drivername} == ${z} ]]; then
echo ${y}
exit 0
fi
done
done
}

# receives chipset family and driver architecture as argument, outputs the 
driver's filename
get_drivername() {
local family=$1
local architecture=$2
echo ${MESA_DRIVERS[${family},${architecture}driver]}
}

# receives the chipset family as argument, outputs the currently selected 
architecture for that family
get_current_implementation() {
local family=$1
local y
local z
local current=$(get_drivername ${family} classic)

if [[ -L ${DRI_DIR}/${current} ]]; then
for y in classic gallium; do
z=$(get_drivername ${family} ${y})
if [[ $(readlink ${DRI_DIR}/${current}) == 
../mesa/${z}  -f ${MESA_DIR}/${z} ]]; then
echo $(drivername_to_architecture ${z})
fi
done
elif [[ -f ${DRI_DIR}/${current} ]]; then
echo classic
fi
}

# receives a family as argument, outputs all installed driver filenames
get_implementations() {
local ret
local family=$1
local y
local z
for y in classic gallium; do
z=$(get_drivername ${family} ${y})
[ -f ${MESA_DIR}/${z} -o -L ${MESA_DIR}/${z} ]  ret+=${y} 
done
echo ${ret}
}

### show action ###
describe_show() {
echo Print the current OpenGL driver.
}

do_show() {
local current
local x
local y
for x in ${MESA_IMPLEMENTATIONS}; do
current=$(get_current_implementation ${x})
if [[ -n ${current} ]]; then
echo -n ${x} 
echo ${current}
fi
done
return 0
}

### list action ###
describe_list() {
echo List the available OpenGL drivers.
}

do_list() {
local x
local y
local z
local available

for x in ${MESA_IMPLEMENTATIONS}; do
write_list_start ${MESA_DRIVERS[${x},description]}
available=( $(get_implementations ${x}) )
for (( i = 0 ; i  ${#availab...@]} ; i = i + 1 )); do
if [[ ${available[${i}]} == 
$(get_current_implementation ${x}) ]]; then
available[${i}]=$(highlight_marker 
${available[${i}]})
fi
write_kv_list_entry ${available[${i}]}
done
done
}

### set action ###
describe_set() {
echo Select the OpenGL driver.
}

describe_set_parameters() {
echo [--auto|family architecture]
}

describe_set_options() {
echo --auto : Sets all drivers which are not already set
echo family : The chipset family, or sw for software renderer
echo architecture : The driver architecture
}

do_set() {
if [[ $1 == --auto ]]; then
local x
for x in ${MESA_IMPLEMENTATIONS}; do

[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2010-10-31 23h59 UTC

2010-10-31 Thread Robin H. Johnson
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2010-10-31 23h59 UTC.

Removals:
net-libs/libjingle  2010-10-27 12:40:43 ssuominen
net-voip/telepathy-stream-engine2010-10-27 12:43:32 ssuominen
media-libs/farsight 2010-10-27 12:45:44 ssuominen
media-plugins/gst-plugins-farsight  2010-10-27 12:46:32 ssuominen
sci-chemistry/msms  2010-10-30 13:25:52 jlec
games-misc/fortune-mod-prolinux 2010-10-30 15:09:34 zzam
dev-tex/achemso 2010-10-31 19:53:49 dilfridge
dev-tex/algorithms  2010-10-31 19:56:27 dilfridge

Additions:
dev-perl/Lchown 2010-10-25 15:17:57 jlec
media-video/stk11xx 2010-10-25 19:28:41 mgorny
dev-ruby/daemon_controller  2010-10-25 19:57:19 graaff
app-misc/enum   2010-10-25 22:45:59 sping
net-misc/rygel  2010-10-26 11:08:19 ford_prefect
x11-misc/arandr 2010-10-26 16:01:15 ssuominen
app-misc/specto 2010-10-26 17:22:44 xmw
dev-python/thunarx-python   2010-10-26 19:59:48 xmw
dev-python/python-cluster   2010-10-26 20:16:43 hwoarang
dev-vcs/rabbitvcs   2010-10-26 20:59:03 xmw
app-shells/autojump 2010-10-26 22:15:00 xmw
x11-plugins/pidgin-privacy-please   2010-10-26 22:58:41 xmw
sys-auth/fprintd2010-10-27 12:10:18 xmw
dev-perl/rename 2010-10-27 14:30:59 ssuominen
dev-vcs/svneverever 2010-10-27 17:15:32 sping
app-portage/fetchcommandwrapper 2010-10-27 20:30:40 sping
app-misc/gtk-sunlight   2010-10-27 23:25:17 xmw
dev-ruby/spruz  2010-10-28 05:58:53 graaff
dev-ruby/file-tail  2010-10-28 06:17:43 graaff
sci-chemistry/pdb-tools 2010-10-28 15:48:14 jlec
sci-chemistry/hollow2010-10-28 20:04:40 jlec
sci-chemistry/msms-bin  2010-10-30 13:17:03 jlec
sci-chemistry/threeV2010-10-30 13:44:13 jlec
games-misc/fortune-mod-flashrider   2010-10-30 15:08:56 zzam
dev-cpp/atkmm   2010-10-30 20:59:53 pacho
dev-perl/Test-Fatal 2010-10-31 09:10:50 tove
sci-libs/cgcode 2010-10-31 10:37:29 jlec
dev-java/ecj-gcj2010-10-31 17:29:23 caster
dev-python/mygpoclient  2010-10-31 17:32:33 ssuominen
dev-php5/pecl-mongo 2010-10-31 19:02:54 olemarkus

--
Robin Hugh Johnson
Gentoo Linux Developer
E-Mail : robb...@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85
Removed Packages:
net-libs/libjingle,removed,ssuominen,2010-10-27 12:40:43
net-voip/telepathy-stream-engine,removed,ssuominen,2010-10-27 12:43:32
media-libs/farsight,removed,ssuominen,2010-10-27 12:45:44
media-plugins/gst-plugins-farsight,removed,ssuominen,2010-10-27 12:46:32
sci-chemistry/msms,removed,jlec,2010-10-30 13:25:52
games-misc/fortune-mod-prolinux,removed,zzam,2010-10-30 15:09:34
dev-tex/achemso,removed,dilfridge,2010-10-31 19:53:49
dev-tex/algorithms,removed,dilfridge,2010-10-31 19:56:27
Added Packages:
dev-perl/Lchown,added,jlec,2010-10-25 15:17:57
media-video/stk11xx,added,mgorny,2010-10-25 19:28:41
dev-ruby/daemon_controller,added,graaff,2010-10-25 19:57:19
app-misc/enum,added,sping,2010-10-25 22:45:59
net-misc/rygel,added,ford_prefect,2010-10-26 11:08:19
x11-misc/arandr,added,ssuominen,2010-10-26 16:01:15
app-misc/specto,added,xmw,2010-10-26 17:22:44
dev-python/thunarx-python,added,xmw,2010-10-26 19:59:48
dev-python/python-cluster,added,hwoarang,2010-10-26 20:16:43
dev-vcs/rabbitvcs,added,xmw,2010-10-26 20:59:03
app-shells/autojump,added,xmw,2010-10-26 22:15:00
x11-plugins/pidgin-privacy-please,added,xmw,2010-10-26 22:58:41
sys-auth/fprintd,added,xmw,2010-10-27 12:10:18
dev-perl/rename,added,ssuominen,2010-10-27 14:30:59
dev-vcs/svneverever,added,sping,2010-10-27 17:15:32
app-portage/fetchcommandwrapper,added,sping,2010-10-27 20:30:40
app-misc/gtk-sunlight,added,xmw,2010-10-27 23:25:17
dev-ruby/spruz,added,graaff,2010-10-28 05:58:53
dev-ruby/file-tail,added,graaff,2010-10-28 06:17:43
sci-chemistry/pdb-tools,added,jlec,2010-10-28 15:48:14
sci-chemistry/hollow,added,jlec,2010-10-28 20:04:40
sci-chemistry/msms-bin,added,jlec,2010-10-30 13:17:03
sci-chemistry/threeV,added,jlec,2010-10-30 13:44:13
games-misc/fortune-mod-flashrider,added,zzam,2010-10-30 15:08:56
dev-cpp/atkmm,added,pacho,2010-10-30 20:59:53
dev-perl/Test-Fatal,added,tove,2010-10-31 09:10:50
sci-libs/cgcode,added,jlec,2010-10-31 10:37:29
dev-java/ecj-gcj,added,caster,2010-10-31 17:29:23