I will commit this patch in 3 days, if there are no other suggestions about
this patch.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
t; use python && python_set_active_version 2
Calling python_pkg_setup() is required in EAPI >=4, so I suggest:
pkg_setup() {
if use python; then
python_set_active_version 2
python_pkg_setup
fi
}
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-10-01 10:30:22 Peter Volkov napisał(a):
> В Птн, 24/09/2010 в 20:09 +0000, Arfrever Frehtes Taifersar Arahesis
> (arfrever) пишет:
> > Added:sympy-0.6.7-python-2.7.patch
> > Log:
> > Fix majority of test failures with Python 2.7 (bug #330713).
&
v-python/nevow
won't be left after uninstallation.
- Unreported bug: Empty directories won't be left after uninstallation.
- Unreported bug: Uninstallation won't fail after uninstallation of given
version of Python.
I'm plannning to commit these patches in 1 week,
2010-10-18 09:06:06 Mike Frysinger napisał(a):
> On October 17, 2010 21:33:20 Arfrever Frehtes Taifersar Arahesis wrote:
> > Subpatch #5 improves some code used in older EAPIs.
>
> does this fix Bug 340395 ?
No. It's not related to that bug.
--
Arfrever Frehte
t reply is going to be "and what are you waiting
> > for, before fixing it?". Seriously.
>
> i guess the answer is that you need someone on the QA team to fix it for you ?
You shouldn't assume, that I can write answers when I'm away.
I will work on a patch.
--
Ar
Subpatch #11 adds temporary support for EAPI="0" in
python_get_implementational_package() to work
around a part of bug #340395.
This subpatch is very small, so I'm planning to commit it with the rest of
subpatches.
--
Arfrever Frehtes Taifersar Arahesis
--- python.eclass
++
2010-10-18 17:26:13 Petteri Räty napisał(a):
> On 10/18/2010 04:33 AM, Arfrever Frehtes Taifersar Arahesis wrote:
>
> > Subpatch #10 fixes exporting of python_pkg_setup() in EAPI >=4.
> >
> > There will be other changes in API of python.eclass in EAPI >=4, so
&
2010-10-24 20:54:56 Petteri Räty napisał(a):
> On 10/24/2010 09:49 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-10-18 17:26:13 Petteri Räty napisał(a):
> >> On 10/18/2010 04:33 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> >>
> >>> Subpatch
Arfrever Frehtes Taifersar Arahesis 2010-10-24 21:22:24 napisał(a):
> 2010-10-24 20:54:56 Petteri Räty napisał(a):
> > On 10/24/2010 09:49 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> > > 2010-10-18 17:26:13 Petteri Räty napisał(a):
> > >> On 10/18/2010 04:33
ures in Portage, so inclusion
of these features
in EAPI="4" wouldn't delay EAPI="4".
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
active version of Python. I would like to encourage other developers to work on
fixing remaining
packages.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> On Mon, 25 Oct 2010 15:24:23 +0200
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 1. Support for "." characters in names of USE flags
>
> If you do this, you'll have to either convert everything using Python
2010-10-25 15:50:23 Peter Volkov napisał(a):
> В Пнд, 25/10/2010 в 15:37 +0200, Arfrever Frehtes Taifersar Arahesis пишет:
> > I would like to suggest that setting Python 3.1 as main active version of
> > Python be officially
> > supported and recommended for Gentoo develo
2010-10-25 15:56:50 Ulrich Mueller napisał(a):
> >>>>> On Mon, 25 Oct 2010, Arfrever Frehtes Taifersar Arahesis wrote:
>
> > 1. Support for "." characters in names of USE flags
>
> Are you aware that this would break existing programs that do rege
y. I think people can understand "python_abis_2_5"
> well enough, besides being happy that their app will KEEP working.
"2_5" is very ugly and unacceptable. python.eclass already uses "2.5" (e.g. in
RESTRICT_PYTHON_ABIS).
--
Arfrever Frehtes Taifersar Arahesi
2010-10-25 16:03:01 Ciaran McCreesh napisał(a):
> On Mon, 25 Oct 2010 15:56:18 +0200
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> > > On Mon, 25 Oct 2010 15:24:23 +0200
> > > Arfrever Frehtes Taifersar Arahesis
2010-10-25 16:37:38 Fabio Erculiani napisał(a):
> Please, just, no.
> Projects and people are just not ready, yet. And even Python experts
> at #python tell to stay away from Py3, last time I checked.
#python channel isn't maintained by Python upstream developers.
--
Arfrever Fre
2010-10-25 16:31:41 Petteri Räty napisał(a):
> On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
> wrote:
> > arfrever10/10/25 11:54:19
> >
> > Modified: python.eclass
> > Log:
> > Set IUSE in EAPI >=4.
2010-10-25 19:16:56 Thilo Bangert napisał(a):
> Arfrever Frehtes Taifersar Arahesis said:
> > 2010-10-25 15:50:23 Peter Volkov napisał(a):
> > > В Пнд, 25/10/2010 в 15:37 +0200, Arfrever Frehtes Taifersar Arahesis
> пишет:
> > > > I would like to suggest that
2010-10-26 02:45:10 Jorge Manuel B. S. Vicetto napisał(a):
> On 25-10-2010 13:37, Arfrever Frehtes Taifersar Arahesis wrote:
> > I would like to suggest that setting Python 3.1 as main active version of
> > Python be officially
> > supported and recommended for Gentoo develo
w profiles etc.
eapi files would still be used to specify EAPI for EAPI-unversioned files in
given profiles.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
acter in package names, then my suggestion
would allow to
handle such packages.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
atisfiable
package.use.force
package.use.mask
package.use.unsatisfiable
packages
virtuals
(Some of these files aren't documented in PMS.)
I would like to suggest that this feature be included in EAPI="4".
I have a patch, which implements this feature in Porta
2010-11-15 19:32:28 Zac Medico napisał(a):
> On 11/15/2010 10:23 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-11-03 06:18:01 Zac Medico napisał(a):
> >> When you need to use a new EAPI, why not just create a sub-profile that
> >> uses the existing 'eapi
2010-10-25 16:03:01 Ciaran McCreesh napisał(a):
> On Mon, 25 Oct 2010 15:56:18 +0200
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> > > On Mon, 25 Oct 2010 15:24:23 +0200
> > > Arfrever Frehtes Taifersar Arahesis
t; Please let me know in case I broke anything.
You probably broke generation of stages :) .
(I have restored a minimal version of eselect_python_update() in python
overlay.)
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-11-16 00:41:35 Alex Alexander napisał(a):
> On Mon, Nov 15, 2010 at 07:40:44PM +0100, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > Some updates to my suggestion:
> > - Files would optionally end with "-${EAPI}" suffix.
> > - The following files would
2010-11-19 16:51:03 Zac Medico napisał(a):
> On 10/25/2010 06:24 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> > use.unsatisfiable and package.use.unsatisfiable files would cause that
> > `repoman` would treat
> > given USE flags in the same way as masked USE flags.
python_abis_2.5? ( dev-lang/python:2.5[threads,xml] )
...
No has_version() checks in python_pkg_setup() will be generated from
PYTHON_DEPEND.
PYTHON_USE_WITH* variables will be banned in EAPI >=4.
Appropriate REQUIRED_USE will be generated from PYTHON_DEPEND.
Examples:
# Unset PYTHON_DEPEND or PYTHON_DEPEND="<<>>" can generate:
REQUIRED_USE="|| ( python_abis_2.4 python_abis_2.5 python_abis_2.6
python_abis_2.7 python_abis_3.0 python_abis_3.0 python_abis_3.1 python_abis_3.2
python_abis_2.5-jython )"
# PYTHON_DEPEND="A? ( B? ( <<[ncurses,threads]>> ) )" can generate:
REQUIRED_USE="A? ( B? ( || ( python_abis_2.4 python_abis_2.5 python_abis_2.6
python_abis_2.7 python_abis_3.0 python_abis_3.0 python_abis_3.1 python_abis_3.2
python_abis_2.5-jython ) ) )"
PYTHON_BDEPEND
I would also like to introduce PYTHON_BDEPEND variable, which will affect only
DEPEND without
RDEPEND. PYTHON_BDEPEND will have the same syntax as PYTHON_DEPEND in given
EAPI and type of
package. PYTHON_BDEPEND maybe won't affect REQUIRED_USE and has_version()
checks in
python_pkg_setup(). PYTHON_BDEPEND won't affect PYTHON_DEPEND's influence on
DEPEND
(dependencies will be concatenated). PYTHON_BDEPEND probably will be used
mainly in packages
not supporting installation for multiple Python ABIs. In packages supporting
installation for
multiple Python ABIs, PYTHON_BDEPEND can be useful only to specify USE
dependencies (e.g. USE
dependencies conditional on "test" USE flag). Unset PYTHON_BDEPEND won't affect
DEPEND.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-11-28 20:59:05 Zac Medico napisał(a):
> On 11/28/2010 10:15 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-11-19 16:51:03 Zac Medico napisał(a):
> >> On 10/25/2010 06:24 AM, Arfrever Frehtes Taifersar Arahesis wrote:
> >>> use.unsatisfiable and package
2010-11-28 21:15:15 Markos Chandras napisał(a):
> On Sun, Nov 28, 2010 at 08:32:16PM +0100, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > I would like to introduce incompatible improvements in syntax of
> > PYTHON_DEPEND variable in
> > EAPI >=4. The new syntax w
2010-11-28 21:20:31 Michał Górny napisał(a):
> On Sun, 28 Nov 2010 20:32:16 +0100
> Arfrever Frehtes Taifersar Arahesis wrote:
>
> > PYTHON_DEPEND will be required. Otherwise each "${range_of_versions}"
> > should be included between "<<" and &q
2010-11-28 21:39:43 Michał Górny napisał(a):
> On Sun, 28 Nov 2010 21:34:49 +0100
> Arfrever Frehtes Taifersar Arahesis wrote:
>
> > 2010-11-28 21:20:31 Michał Górny napisał(a):
> > > On Sun, 28 Nov 2010 20:32:16 +0100
> > > Arfrever
2010-11-28 21:30:47 Zac Medico napisał(a):
> On 11/28/2010 12:07 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-11-28 20:59:05 Zac Medico napisał(a):
> >> It seems like you're trying to bypass an important function of repoman
> >> though. The idea is tha
2010-11-29 01:26:19 Robin H. Johnson napisał(a):
> Presently in package.mask, we have this entry:
>
> # Arfrever Frehtes Taifersar Arahesis (04 Jul 2010)
> # Python 2.7 masked until sufficient number of reverse dependencies is fixed.
> ~dev-lang/python-2.7
>
> Well Pytho
2010-11-29 01:24:50 Alex Alexander napisał(a):
> On 28 Nov 2010, at 22:20, Michał Górny wrote:
>
> > On Sun, 28 Nov 2010 20:32:16 +0100
> > Arfrever Frehtes Taifersar Arahesis wrote:
> >
> >> PYTHON_DEPEND will be required. Otherwise each "${range_of_vers
omebody else wasn't planning to use "{...}"
in the future.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-11-29 08:39:46 Sebastian Pipping napisał(a):
> On 11/28/10 19:04, Arfrever Frehtes Taifersar Arahesis wrote:
> > You probably broke generation of stages :) .
> > (I have restored a minimal version of eselect_python_update() in python
> > overlay.)
>
> Could yo
2010-11-29 12:43 Sebastian Pipping napisał(a):
> On 11/29/10 02:35, Arfrever Frehtes Taifersar Arahesis wrote:
>> Sebastian Pipping recently removed automatic upgrade of active version of
>> Python, so
>> python-2.7.1.ebuild does not upgrade active version of Python.
>
test given modules/scripts with multiple
Python versions,
would need dependencies built with support for more Python versions.
- You might break something outside of python.eclass.
There is a plan (and patches) to introduce usage of USE flags for selection of
requested
Python versions. It w
Why does waf-utils_pkg_setup() call 'python_set_active_version 2'?
What do you plan to do when there are packages using waf and supporting Python
3?
http://code.google.com/p/waf/ says:
"compatibility from Python 2.3 to 3.1 is maintained (and Jython 2.5)"
--
Arfrever Frehte
==
There are already existing patches for Portage, which implement these
solutions, which are
suggested new features in EAPI="4".
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2010-12-18 03:48:26 Donnie Berkholz napisał(a):
> On 02:45 Sat 18 Dec , Arfrever Frehtes Taifersar Arahesis wrote:
> > Problem #1: USE flags cannot contain "." characters.
>
> This isn't a problem, it's an arbitrary statement of an antifeature. My
> un
; added the webapp.eclass does some things.
What do you mean about python.eclass?
python.eclass doesn't define python_src_unpack().
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
remaining ebuilds using distutils.eclass,
python_mod_optimize() or
python_mod_cleanup() in old EAPIs, then it will be possible to remove large
parts of
python_mod_optimize() and python_mod_cleanup().
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
ad on my side which I have no real
> benefit
> from and I have no real clue about how to write proper EAPI-3 ebuilds.
You can use EAPI="3" without supporting prefix installations.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2011-02-13 20:43:12 Fabian Groffen napisał(a):
> On 13-02-2011 16:53:40 +0000, Arfrever Frehtes Taifersar Arahesis wrote:
> > arfrever11/02/13 16:53:40
> >
> > Modified: make.defaults
> > Log:
> > Don't include ${USE} in the first assignment to US
https://bugs.gentoo.org/show_bug.cgi?id=python-3.2
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
pport that EAPI.
>
> What do you think?
python.eclass maintainers are (slowly) working on support for EAPI="4". Please
wait patiently.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
pkg_postrm()
--
Arfrever Frehtes Taifersar Arahesis
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
# @ECLASS: python-namespaces.eclass
# @MAINTAINER:
# Gentoo Python Project
# @BLURB: Eclass for packages installing Python
y")
Subpatch #11 adds sanity checks for arguments in some functions.
Subpatch #12 adds unsetting of some internal functions after using of them.
Subpatch #13 moves declaration of local variables to other places for
consistency with
python.eclass.
I'm planning to commit this patch in 1
2011-04-03 21:28:02 Tomáš Chvátal napisał(a):
> Dne 3.4.2011 19:38, Arfrever Frehtes Taifersar Arahesis napsal(a):
> > I would like to add python-namespaces.eclass. This eclass will be used by a
> > small number of
> > special packages, which will provide Python namespaces
2011-04-04 12:04:44 Tomáš Chvátal napisał(a):
> Dne 4.4.2011 01:13, Arfrever Frehtes Taifersar Arahesis napsal(a):
> > 2011-04-03 21:28:02 Tomáš Chvátal napisał(a):
> >> Dne 3.4.2011 19:38, Arfrever Frehtes Taifersar Arahesis napsal(a):
> >>> I would like to add
ope/namespaces-silva
net-zope/namespaces-zc
net-zope/namespaces-z3c
The following packages will use both distutils.eclass and
python-namespaces.eclass:
dev-python/dap
dev-python/flask
dev-python/logilab-common
dev-python/paste
net-zope/kss-core
--
Arfrever Frehtes Taifersar Arahesis
signature.
defines phase functions for packages
> > installing Python namespaces.
>
> ^^^ This isn't a useful description.
IMHO it's sufficient, but could you suggest some sentences of description?
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2011-05-01 00:32:13 Brian Harring napisał(a):
> On Sat, Apr 30, 2011 at 11:27:47PM +0200, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > 2011-04-04 13:48:43 Brian Harring napisał(a):
> > > > # @ECLASS: python-namespaces.eclass
> > > > # @MAINTAI
gelogs from Manifests and
> live with that. You have your changelogs unprotected but you keep your
> ebuilds safe(?). As I said, it is a balanced choice that has to be made.
Generated ChangeLogs could contain server-side-generated signatures for
themselves
(gpg --sign --clearsign ChangeLog && mv ChangeLog.asc ChangeLog).
(Manifests wouldn't contain entries for ChangeLogs.)
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
;):
xml.use_pyxml()
This code works with previous versions of Python, so no changes in
dependencies are needed.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2011-05-11 12:30:18 Tomáš Chvátal napisał(a):
> Dne 10.5.2011 23:21, Arfrever Frehtes Taifersar Arahesis napsal(a):
> > PyXML is dead:
> > http://mail.python.org/pipermail/xml-sig/2004-November/010735.html
> > http://mail.python.org/pipermail/xml-sig/2006-June/0115
2011-05-17 19:32:23 Markos Chandras napisał(a):
> On Tue, May 17, 2011 at 01:11:57PM -0400, Mark Loeser wrote:
> > Arfrever Frehtes Taifersar Arahesis said:
> > > PyXML is dead:
> > > http://mail.python.org/pipermail/xml-sig/2004-November/010735.html
> > >
2011-05-17 19:11:57 Mark Loeser napisał(a):
> Arfrever Frehtes Taifersar Arahesis said:
> > PyXML is dead:
> > http://mail.python.org/pipermail/xml-sig/2004-November/010735.html
> > http://mail.python.org/pipermail/xml-sig/2006-June/011545.html
> >
> > PyXM
2011-05-17 20:24:16 Mark Loeser napisał(a):
> Arfrever Frehtes Taifersar Arahesis said:
> > > I second that. Why do we need to make all the work fixing packages
> > > instead of letting upstream do their job? I am not so excited to
> > > fix every package I maint
2011-05-17 20:43:29 Tomáš Chvátal napisał(a):
> Dne 10.5.2011 23:21, Arfrever Frehtes Taifersar Arahesis napsal(a):
> > PyXML is dead:
> > http://mail.python.org/pipermail/xml-sig/2004-November/010735.html
> > http://mail.python.org/pipermail/xml-sig/2006-June/0115
2011-05-17 21:21:48 Tomáš Chvátal napisał(a):
> Dne 17.5.2011 21:12, Arfrever Frehtes Taifersar Arahesis napsal(a):
> > 2011-05-17 20:43:29 Tomáš Chvátal napisał(a):
> >> Dne 10.5.2011 23:21, Arfrever Frehtes Taifersar Arahesis napsal(a):
> >>> PyXML is dead:
calling scanelf on all installed files.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
or
/etc/portage/env/${CATEGORY}/${PN}:${SLOT}.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
urces bindings/python
build_python_bindings() {
emake \
PYTHON_INCLUDES="$(python_get_includedir)" \
PYTHON_SITE_PACKAGES="$(python_get_sitedir)" \
python_bindings
}
python_execute_function -s --source-dir b
years and will
(slowly) replace
PSF-2.2, PSF-2.3, PSF-2.4 and PYTHON in values of LICENSE in ebuilds.
I'm attaching suggested PSF-2 file based on LICENSE file from default branch of
Python upstream
repository.
--
Arfrever Frehtes Taifersar Arahesis
PYTHON SOFTWARE FOUNDATION LI
ocedure will apply.
> >>
> >
> > About the concrete case of python eclass, per Arfrever's comment in bug
> > report related with its eapi4 support, that support is already available
> > in overlay, but not yet merged to the tree (probably because of the
>
is
EAPI-independent, so there is no need for a new eclass.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a133cb89d5279df7febcd0c8ab3890e2ccfb897a
> Maybe we need to spec VDB after all to avoid that kind of nonsense.
I think that unmerge-orphans is a useful feature.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
x86 to overlay.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
te_installation_images() renames them (so that their
names include
Python ABI), calls python_convert_shebangs() if they don't have appropriate
shebangs, and calls
python_generate_wrapper_scripts() to create appropriate wrapper scripts).
--
Arfrever Frehtes Taifersar Arahesis
signatu
ason for Gentoo to be worse than Exherbo and not allow dots in
USE flags.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2011-09-16 01:54:44 Brian Harring napisał(a):
> On Fri, Sep 16, 2011 at 01:21:55AM +0200, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > 2011-09-15 09:55:08 Ciaran McCreesh napisał(a):
> > > On Thu, 15 Sep 2011 09:35:21 +0200
> > > Michał Górny wrote:
> >
2011-11-26 11:58:22 Fabian Groffen napisał(a):
> On 26-11-2011 01:54:35 +0000, Arfrever Frehtes Taifersar Arahesis wrote:
> > commit: 1d4ac47c28706094230cb2c4e6ee1c1c71629aa0
> > T> Org>
> > AuthorDate: Sat Nov 26 01:52:49 2011 +0000
> > Commit: Arfrever F
hat with a
> few points: (1) i don't think there are any packages in the tree that have
> optional neon (the library) support
http://qa-reports.gentoo.org/output/genrdeps/rindex/net-libs/neon lists 6
packages, which optionally
depend on net-libs/neon.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
+ configure.ac || die "fixing CFLAGS failed!"
The broken libuv-1.2.1.ebuild was not disabling unwanted addition of -g to
CFLAGS.
The fix for this problem affected installed files, so revision bump was
required.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
Maybe one generic function (called e.g. tc-set-linker) whose arguments
are a preference-ordered list of supported linkers?
If currently used linker is not in the specified list, then this
function would force using first found linker from that list.
Forcing bfd only:
tc-set-linker bfd
Forcing g
llvm-libunwind - Use sys-libs/llvm-libunwind instead of sys-libs/libunwind
This would be similar to graphicsmagick and libressl USE flags.
sys-libs/libunwind and sys-libs/llvm-libunwind are ABI-incompatible,
at least due to different sonames of libraries. Switching between them
requires rebuildin
201 - 281 of 281 matches
Mail list logo