public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Installation of static libraries, USE=static-libs proposal
Date: Sun, 20 Jul 2008 15:40:01 +0400	[thread overview]
Message-ID: <1216554002.4891.85.camel@camobap> (raw)
In-Reply-To: <1214877951.29224.54.camel@localhost>

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

В Втр, 01/07/2008 в 05:05 +0300, Mart Raudsepp пишет:
> Over a year or two ago, it was communicated that it supposedly a policy
> that USE=static

Well, I don't have web-reference at hand now, but there was a thread in
gentoo-dev with the subject: "Say no to static libraries!". Summarizing
some ideas from there:

1. Some packages will break if you build their deps with USE=static.
This can be fixed when we start to use USE-deps in the tree.

2. We already have mechanism to make what you want. Just drop
EXTRA_ECONF="--disable-static" into your make.conf and to workaround
problem stated in point 1 use

EXTRA_ECONF="${EXTRA_ECONF/--disable-static}" 

in /etc/portage/env/cat/pkg. (For those who interested  list of packages
for which I have to filter --disable-static is in attachment).


Well, I'm using EXTRA_ECONF for more then year now and I'd like to say
that it's not perfect solution. Not all packages are autotools based and
ignore --disable-static and now I have 103M of static libs on my
desktop. So now I'm all for having static-libs USE flag. But please,
don't do that on per-package base. Make an eclass for that. Think about
not-autotools packages, and don't put it in the tree until we start
using USE deps.


Thanks for reiterating this discussion. I wanted to return to it soon as
seems that USE deps are really about to enter our life.

And BTW, seems that all gnome packages obey EXTRA_ECONF ;)

-- 
Peter.

[-- Attachment #2: disable-static-broken-packages.list --]
[-- Type: text/plain, Size: 216 bytes --]

dev-libs/popt
dev-libs/lzo
dev-libs/libpcre
dev-libs/xmlrpc-c
dev-libs/libol
media-libs/pdflib
media-sound/audacity
sys-devel/gdb
sys-devel/libtool
sys-apps/ed
sys-apps/ed
sys-fs/fuse
dev-ruby/rcairo
dev-ruby/rcairo

  parent reply	other threads:[~2008-07-20 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  2:05 [gentoo-dev] RFC: Installation of static libraries, USE=static-libs proposal Mart Raudsepp
2008-07-01  8:26 ` [gentoo-dev] " Duncan
2008-07-01  9:33   ` Rémi Cardona
2008-07-01 12:45     ` Mart Raudsepp
2008-07-01 12:57       ` Enrico Weigelt
2008-07-01 22:34         ` Rémi Cardona
2008-07-20 11:40 ` Peter Volkov [this message]
2008-10-21 23:40   ` [gentoo-dev] " Mart Raudsepp

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=1216554002.4891.85.camel@camobap \
    --to=pva@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