Make the gnome2_icon_cache_update function update all icon themes rather
than depending on gnome2_icon_savelist to select themes to update. This
makes the function easier to use whenever the developer needs it
explicitly (i.e. knows that themes are installed), while the overhead of
regenerating mul
---
eclass/gnome2.eclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/eclass/gnome2.eclass b/eclass/gnome2.eclass
index 8a83297b0959..feb6301221ea 100644
--- a/eclass/gnome2.eclass
+++ b/eclass/gnome2.eclass
@@ -337,7 +337,9 @@ gnome2_pkg_preinst() {
gnome2_pkg_postinst(
---
eclass/xfconf.eclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/eclass/xfconf.eclass b/eclass/xfconf.eclass
index 2655420ddd35..b91d0fe1eda3 100644
--- a/eclass/xfconf.eclass
+++ b/eclass/xfconf.eclass
@@ -139,7 +139,9 @@ xfconf_pkg_postinst() {
debug-print-
---
eclass/kde5.eclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/eclass/kde5.eclass b/eclass/kde5.eclass
index 106383bb05c3..9ed664be60c7 100644
--- a/eclass/kde5.eclass
+++ b/eclass/kde5.eclass
@@ -704,7 +704,9 @@ kde5_pkg_preinst() {
kde5_pkg_postinst() {
de
---
eclass/kde4-base.eclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/eclass/kde4-base.eclass b/eclass/kde4-base.eclass
index 999c8a05fee2..97f4dfd4eda9 100644
--- a/eclass/kde4-base.eclass
+++ b/eclass/kde4-base.eclass
@@ -907,7 +907,9 @@ kde4-base_pkg_preinst() {
kd
---
eclass/chromium.eclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/eclass/chromium.eclass b/eclass/chromium.eclass
index 5f8c53cabf35..fcc02dd6e028 100644
--- a/eclass/chromium.eclass
+++ b/eclass/chromium.eclass
@@ -120,7 +120,7 @@ chromium_remove_language_paks() {
}
---
eclass/gnome2-utils.eclass | 5 -
1 file changed, 5 deletions(-)
diff --git a/eclass/gnome2-utils.eclass b/eclass/gnome2-utils.eclass
index 7db092e1ec66..a89b9885c391 100644
--- a/eclass/gnome2-utils.eclass
+++ b/eclass/gnome2-utils.eclass
@@ -230,11 +230,6 @@ gnome2_icon_cache_update() {
On czw, 2017-04-13 at 07:39 +0200, Michał Górny wrote:
> Officially list the slot="" attribute that is used in GLSAs for quite
> some time in the DTD. It is supported by Portage and gentoolkit for
> a long time, and was used in GLSAs interchangeably with implicit
> appended
is "find -ipath" but
> +# this does not intelligently skip non-matching paths, making it
> +# slow. Case-insensitive matching can only be applied to patterns so
> +# extended globbing is used to turn regular strings into patterns. All
> +# special characters are escaped so don
gument any more with today's large disks.
>
I think the eclass supports multiple different CD variants (releases),
including poorly made copies, copy-protected media... I don't think you
can create a file with stable checksum out of them in any sane way.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
Dnia 18 kwietnia 2017 23:31:31 CEST, James Le Cuirot
napisał(a):
>On Tue, 18 Apr 2017 08:08:44 +0200
>Michał Górny wrote:
>
>> On pon, 2017-04-17 at 22:53 +0100, James Le Cuirot wrote:
>> > diff --git a/eclass/cdrom.eclass b/eclass/cdrom.eclass
>> > index
dd that to the python-exec doc [1]. It's possible it's already
somewhere in the docs but I can't find it ;-).
[1]:https://wiki.gentoo.org/wiki/Project:Python/python-exec
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
Use plain 'pythonX.Y-config' executable name in the python-config
wrapper instead of querying the complete PYTHON_CONFIG path from
python_export.
Constructing full PYTHON_CONFIG path requires querying ABIFLAGS which
requires the Python interpreter to be installed, which in turn
unnecessarily force
Respect EROOT when running gtk-query-immodules-* tools, alike other
updaters in the eclass. This ensures that x11-libs/gtk+ installs
correctly when installing to a ROOT.
---
eclass/gnome2-utils.eclass | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/eclass/gnome2-utils.e
# Michał Górny (22 Apr 2017)
# Discontinued, replaced by dev-python/bcolz. No reverse dependencies
# left. Removal in 30 days. Bug #564878.
dev-python/blz
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On sob, 2017-04-22 at 13:43 -0400, Mike Gilbert wrote:
> On Sat, Apr 22, 2017 at 4:20 AM, Michał Górny wrote:
> > Respect EROOT when running gtk-query-immodules-* tools, alike other
> > updaters in the eclass. This ensures that x11-libs/gtk+ installs
> > correctly when
at least 100 characters.
>
> Oh wait, weren't you going to title this about period mark at the end
> of DESCRIPTION...?
Proper sentences end (those with a subject noun and a verb) with a full
stop. The other thingies (sorry, don't know the English name for it) do
not. Simple as that.
ions of setting them
as system-wide compilers.
What do you think?
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
/starcluster
dev-python/xonsh
dev-util/cdiff
media-gfx/svg2rlg
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On pią, 2017-04-14 at 19:25 +0200, Michał Górny wrote:
> Replace the unnecessary use of extglob to strip file suffix
> in make_desktop_entry with a plain ${x%.*}. This is pretty much
> equivalent since match to one of the pre-defined suffixes is already
> confirmed via the preceding
On pią, 2017-04-14 at 21:32 +0200, Michał Górny wrote:
> Stop inheriting the epunt-cxx eclass in eutils implicitly. All the uses
> in ::gentoo are fixed already, and this lets us add extra dependencies
> in the eclass without affecting most of the packages out there.
> ---
> eclas
On pon, 2017-04-17 at 13:07 +0200, Michał Górny wrote:
> Make the gnome2_icon_cache_update function update all icon themes rather
> than depending on gnome2_icon_savelist to select themes to update. This
> makes the function easier to use whenever the developer needs it
> explicitly
On pią, 2017-04-21 at 16:11 +0200, Michał Górny wrote:
> Use plain 'pythonX.Y-config' executable name in the python-config
> wrapper instead of querying the complete PYTHON_CONFIG path from
> python_export.
>
> Constructing full PYTHON_CONFIG path requires querying ABIF
On śro, 2017-04-26 at 11:42 +0200, Chí-Thanh Christopher Nguyễn wrote:
> Michał Górny schrieb:
> > The most important goal of having the packages masked is that it would
> > cause Portage to verbosely complain whenever the users have it
> > installed. With appropriate comment
that
does not affect installed files.
What do you think? Any other ideas?
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
Dnia 27 kwietnia 2017 23:42:34 CEST, Alexis Ballier
napisał(a):
>On Thu, 27 Apr 2017 16:14:13 +0200
>Michał Górny wrote:
>
>> b. those tests can easily be enabled, and that fact is recorded
>> in the installed package metadata,
>>
>> c. the flag can easily be
lly if I don't give a damn about them.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
Add a @SUPPORTED_EAPIS tag that can be used to explicitly provide a list
of EAPIs that are supported by the eclass. The main goal is to make it
possible to extract this list with relative ease, for scripting
purposes. It is not included explicitly in the manpages at the moment.
The first use case
---
eclass/python-r1.eclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index df57cf1e1322..c8d025bcb13c 100644
--- a/eclass/python-r1.eclass
+++ b/eclass/python-r1.eclass
@@ -7,6 +7,7 @@
# @AUTHOR:
# Author: Michał Górny
# Based on
On pią, 2017-04-28 at 16:06 +0200, Michał Górny wrote:
> Add a @SUPPORTED_EAPIS tag that can be used to explicitly provide a list
> of EAPIs that are supported by the eclass. The main goal is to make it
> possible to extract this list with relative ease, for scripting
> purpose
Change the unset value tag to '@DEFAULT-UNSET' to ensure consistent use
of hyphen/underscore throughout eclassdoc. Before, one tag
(@ECLASS-VARIABLE) has used hyphen while also one (@DEFAULT_UNSET) used
underscore. Unify them to use the former since @ECLASS-VARIABLE tag is
more common (and hyphens
Add a @SUPPORTED-EAPIS tag that can be used to explicitly provide a list
of EAPIs that are supported by the eclass. The main goal is to make it
possible to extract this list with relative ease, for scripting
purposes. It is not included explicitly in the manpages at the moment.
The first use case
---
eclass/python-r1.eclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index df57cf1e1322..9f56c6f3877a 100644
--- a/eclass/python-r1.eclass
+++ b/eclass/python-r1.eclass
@@ -7,6 +7,7 @@
# @AUTHOR:
# Author: Michał Górny
# Based on
Add a few additional variable classes to better emphasize the specifics
of different kinds of variables set for eclasses, and by eclasses.
The change applied, each eclass variable can belong to one of
the following five eclasses:
1. (default) - variable set by ebuild, influences eclass behavior.
---
eclass/python-r1.eclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index 9f56c6f3877a..866f49071147 100644
--- a/eclass/python-r1.eclass
+++ b/eclass/python-r1.eclass
@@ -55,6 +55,7 @@ inherit multibuild python-utils-r1
fi
# @
On pią, 2017-04-28 at 15:11 -0400, Michael Orlitzky wrote:
> On 04/28/2017 10:59 AM, Michał Górny wrote:
> > Add a few additional variable classes to better emphasize the specifics
> > of different kinds of variables set for eclasses, and by eclasses.
> >
> > The
On sob, 2017-04-29 at 05:41 +0200, Ulrich Mueller wrote:
> > > > > > On Fri, 28 Apr 2017, Michał Górny wrote:
> > (and hyphens do not require holding shift).
>
> So they are awkward to type inside a string that is all-caps?
>
Funny enough, yes. I na
Dnia 29 kwietnia 2017 19:23:49 CEST, Davide Pesavento
napisał(a):
>On Sat, Apr 29, 2017 at 1:57 AM, Michał Górny
>wrote:
>> On sob, 2017-04-29 at 05:41 +0200, Ulrich Mueller wrote:
>>> > > > > > On Fri, 28 Apr 2017, Michał Górny wrote:
>>>
Fix the eclass code to remove the misguided Linux conditionals.
The whole purpose of the eclass was to avoid having to implement
fallback logic for systems not having service manager tmpfiles.d
support. Making it conditional to Linux implied that for non-Linux
systems (Prefix, FreeBSD) we would hav
---
eclass/tmpfiles.eclass | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/eclass/tmpfiles.eclass b/eclass/tmpfiles.eclass
index 9cf040de987f..018ea45d4182 100644
--- a/eclass/tmpfiles.eclass
+++ b/eclass/tmpfiles.eclass
@@ -110,7 +110,18 @@ tmpfiles_process() {
Replace the use of systemd.eclass with more generic tmpfiles.eclass to
install the tmpfiles.d file. Use tmpfiles_process to ensure that
the directory is created and correctly owned instead of keepdir-ing it
(which triggers QA warnings from Portage) and chown-ing it
in pkg_postinst() (which is a hac
/null
+++ b/eclass/ninja-utils.eclass
@@ -0,0 +1,57 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+# @ECLASS: ninja-utils.eclass
+# @MAINTAINER:
+# Michał Górny
+# Mike Gilbert
+# @AUTHOR:
+# Michał Górny
+# Mike Gilbert
+# @BLURB
---
eclass/cmake-utils.eclass | 52 +++
1 file changed, 3 insertions(+), 49 deletions(-)
diff --git a/eclass/cmake-utils.eclass b/eclass/cmake-utils.eclass
index 07f719a62a8c..2b3c8d933d1a 100644
--- a/eclass/cmake-utils.eclass
+++ b/eclass/cmake-utils.
---
sys-apps/systemd/systemd-.ebuild | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/sys-apps/systemd/systemd-.ebuild
b/sys-apps/systemd/systemd-.ebuild
index 7ff69d75cc9a..b4e1f943a599 100644
--- a/sys-apps/systemd/systemd-.ebuild
+++ b/sys-apps/sy
---
www-client/chromium/chromium-59.0.3067.0.ebuild | 19 +--
1 file changed, 1 insertion(+), 18 deletions(-)
diff --git a/www-client/chromium/chromium-59.0.3067.0.ebuild
b/www-client/chromium/chromium-59.0.3067.0.ebuild
index fb975c22b0cd..ac00f473bf45 100644
--- a/www-client/ch
On nie, 2017-04-30 at 06:03 +1200, Kent Fredric wrote:
> On Fri, 28 Apr 2017 16:39:45 +0200
> Michał Górny wrote:
>
> > Change the unset value tag to '@DEFAULT-UNSET' to ensure consistent
> > use of hyphen/underscore throughout eclassdoc. Before, one tag
> &g
On sob, 2017-04-29 at 14:05 -0400, Davide Pesavento wrote:
> On Sat, Apr 29, 2017 at 1:40 PM, Michał Górny wrote:
> > Dnia 29 kwietnia 2017 19:23:49 CEST, Davide Pesavento
> > napisał(a):
> > > On Sat, Apr 29, 2017 at 1:57 AM, Michał Górny
> > > wrote:
> >
e_function() {
> print ""
> print "Return value: " funcret
> }
>+ if (funcout != "") {
>+ if (desc !="")
>+ print ""
>+ print "Outputs: " funcout
>+ }
Move this above return value. Functions usually output before returning.
>
> if (blurb == "")
> fail(func_name ": no @BLURB found")
--
Best regards,
Michał Górny (by phone)
rn(var_name ": unable to extract default
> variable content: " $0)
> val = ""
>- } else if (val !~ /^["']/ && val ~ / /) {
>+ } else if (val !~ /^["']/ && val ~ / /) {
> if (default_unset == 1)
> warn(var_name ": marked as unset, but has
> value: " val)
> val = "\"" val "\""
>- }
> }
> if (length(val))
> val = " " op " \\fI" val "\\fR"
--
Best regards,
Michał Górny (by phone)
Dnia 1 maja 2017 09:32:40 CEST, Ulrich Mueller napisał(a):
>>>>>> On Sun, 30 Apr 2017, Michał Górny wrote:
>
>> From now on I'm not going to listen to any suggestions that do not
>> come with a patch.
>
>You have posted a patch for review. So IMHO, as
ean.
That being the case, I don't really see an advantage of explicitly
listing default value with potentially confusing syntax when the same
problem was already solved in a readable and non-confusing way by
explaining it in the body.
In other words, I don't think that:
DIST_TEST
+# Michał Górny (01 May 2017)
+# Used only by old (removed) versions of dev-python/google-apitools.
+# Last release in 2015. Removal in 30 days.
+dev-python/protorpc
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On wto, 2017-05-02 at 09:38 -0500, William Hubbs wrote:
> On Sun, Apr 30, 2017 at 09:06:53PM +0200, Michał Górny wrote:
> > Fix the eclass code to remove the misguided Linux conditionals.
> > The whole purpose of the eclass was to avoid having to implement
> > fallback logic f
on2_[56]|python3_[123789])
> return 1
> ;;
> pypy|pypy3)
Sounds like a very bad idea. How can you even think of adding
an implementation if you don't know what the eclass API for it would be?
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On wto, 2017-05-02 at 12:11 -0700, Zac Medico wrote:
> On Tue, May 2, 2017 at 12:01 PM, Michał Górny wrote:
>
> > On wto, 2017-05-02 at 11:49 -0700, Zac Medico wrote:
> > > Add forward compatibility up to python3.9. It's helpful to allow some
> > > flexibili
> }
>
> # @FUNCTION: meson_src_compile
> # @DESCRIPTION:
> # This is the meson_src_compile function.
> meson_src_compile() {
> debug-print-function ${FUNCNAME} "$@"
>
> eninja -v -C "${BUILD_DIR}" || die
eninja dies on its own in EAPI 4+.
-n ${PYTHON_IMPLS_NO_STRICT} ]] && return
>1
>> die "Invalid implementation in PYTHON_COMPAT:
>> ${impl}"
>> esac
>> }
>> --
>> 2.10.2
>>
>>
>If nobody objects, I'd like to merge this sometime next week.
If there's no explicit hurry, I'd like to commit it along with other python
patch I'll be writing soon, to avoid multiple cache regens.
--
Best regards,
Michał Górny (by phone)
;;
> *) die "EAPI=${EAPI} is not supported" ;;
> esac
>
> EXPORT_FUNCTIONS src_configure src_compile src_test src_install
>
> if [[ -z ${_MESON_ECLASS} ]]; then
> _MESON_ECLASS=1
>
> inherit ninja-utils
Extra tab on front of the line.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
Add a check for *-nspkg.pth files indicating implicit setuptools
namespace hack. While they kept namespaces somewhat working without
requiring explicit support in ebuilds, they were unreliable. They
frequently required additional hacks (distutils_install_for_testing) to
get the tests working, and t
Prefix the _clean_egg_info function with an appropriate namespace,
and document its purpose with eclassdoc format. Be more verbose
on the exact problem being solved; remove URL to old upstream bug
tracker that no longer exists.
---
eclass/distutils-r1.eclass | 14 +-
1 file changed, 9
keywords like 'testing'
and 'unstable'; they're going to be confusing long-term (compare:
the mess with stable/exp/dev for profiles). But I don't have a very good
idea how to it better right now.
3. What is the use case for 'broken'? Are we ever going to
these archs
> to unstable/exp profiles for the next Council meeting, explicitly
> overriding any arch concerns that are likely to awake now and going to
> be running around like headless chicken.
>
I'm against. Turning more arches into dev/exp only introduces hidden
depgraph breakages.
tiple large stablereqs for
stuff where we need to stabilize newer while some arches are still two
stabilizations behind.
Not to mention when we want to stabilize a new version but the arches still
haven't even keyworded it...
>
>Cheers,
>
>Dirkjan
--
Best regards,
Michał Górny (by phone)
ly to:
python_moduleinto foo/bar
4. gives example use for 3.
--
Best regards,
Michał Górny
Remove the bit of old python_moduleinto documentation that has been
accidentally left over.
---
eclass/python-utils-r1.eclass | 6 --
1 file changed, 6 deletions(-)
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass
index 66a359e8daee..c46feb08449b 100644
--- a/eclass/
Clearly indicate that python_moduleinto can be safely called outside
of the environment with Python interpreter established, and that
a single call can set the correct relative path for multiple different
implementations.
---
eclass/python-utils-r1.eclass | 6 ++
1 file changed, 6 insertions(+
Allow specifying the relative package destination using the dot-notation
used by Python itself (e.g. 'foo.bar') in addition to the directory form
('foo/bar'). Since dot can not be used in Python package names, this
change is backwards-compatible.
---
eclass/python-utils-r1.eclass | 6 --
1 fil
---
dev-python/repoze-who/repoze-who-2.2-r1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-python/repoze-who/repoze-who-2.2-r1.ebuild
b/dev-python/repoze-who/repoze-who-2.2-r1.ebuild
index f2f3ac568592..fb3636b8fe99 100644
--- a/dev-python/repoze-who/repoze-who
Allow two special values in the implementation patterns for
_python_impl_matches(): -2 to indicate all Python 2-compatible
implementations, and -3 to indicate all Python 3-compatible
implementations. Both of those values are implemented using
the python_is_python3 function.
This is mostly meant to
---
virtual/python-futures/python-futures-0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtual/python-futures/python-futures-0.ebuild
b/virtual/python-futures/python-futures-0.ebuild
index 094a0c6dbdd8..d810a9cc3261 100644
--- a/virtual/python-futures/python-future
---
virtual/python-dnspython/python-dnspython-1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/virtual/python-dnspython/python-dnspython-1.ebuild
b/virtual/python-dnspython/python-dnspython-1.ebuild
index 063bbe7ce66f..885153f90caf 100644
--- a/virtual/python-dnspy
On śro, 2017-05-10 at 14:15 -0700, Patrick McLean wrote:
> On Wed, 10 May 2017 20:53:31 +0200
> Michał Górny wrote:
>
> > Allow two special values in the implementation patterns for
> > _python_impl_matches(): -2 to indicate all Python 2-compatible
> > implementati
h less implementations than its reverse dependencies
is a corner case. It's not really worth spending hours making sure
depends are 100% strictly correct. The more important goal is to have
things working reliably, and overspecified deps are reliable, i.e.
packages won't fail to build because of them.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
kages. If that is an issue that package's flag could be renamed
> to "libunwind" as sys-libs/libcxx et al. currently use.
>
Yeah, that makes sense.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On pią, 2017-05-12 at 13:20 +0700, Alex Turbov wrote:
> On Thu, May 11, 2017 at 2:51 PM, Michał Górny wrote:
>
> > Hi,
> >
> > Few janitorial notes for a start:
> >
> > 1. please fix your line wrapping since your messages are wrapped twice
> > now
t least it doesn't introduce a new API.
So I'd like others to chime in and let me know whether they consider
this a worthwhile addition before I start working on it.
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On pią, 2017-05-12 at 17:42 -0700, Daniel Campbell wrote:
> On 05/11/2017 12:51 AM, Michał Górny wrote:
> > In fact, I'm personally leaning towards not building docs at all
> > in ebuilds. It's practically a wasted effort since most of the time
> > users read doc
onent:Keywording (was
> [old] ...) and it didn't show up on my radar, nor on x86s.
>
Why would you expect to developers spend their effort on moving bugs to
new keywording workflow *after* the arch teams have been neglecting them
for 1.5 years?
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
# @DEAD
# Michał Górny (16 May 2017)
# gst-plugins* eclasses are no longer used. They will be removed
# in 30 days.
gst-plugins-bad.eclass
gst-plugins-base.eclass
gst-plugins-good.eclass
gst-plugins-ugly.eclass
gst-plugins10.eclass
--
Best regards,
Michał Górny
signature.asc
Description: This
On nie, 2017-04-30 at 22:28 +0200, Michał Górny wrote:
> ---
> eclass/ninja-utils.eclass | 57
> +++
> 1 file changed, 57 insertions(+)
> create mode 100644 eclass/ninja-utils.eclass
>
> diff --git a/eclass/ninja-utils.
;;
> *)
> + [[ -n ${PYTHON_IMPLS_NO_STRICT} ]] && return 1
> die "Invalid implementation in PYTHON_COMPAT: ${impl}"
> esac
> }
I've changed the name to PYTHON_COMPAT_NO_STRICT to fit
On pią, 2017-05-05 at 23:14 +0200, Michał Górny wrote:
> Add a check for *-nspkg.pth files indicating implicit setuptools
> namespace hack. While they kept namespaces somewhat working without
> requiring explicit support in ebuilds, they were unreliable. They
> frequently required addi
On pią, 2017-05-05 at 23:28 +0200, Michał Górny wrote:
> Prefix the _clean_egg_info function with an appropriate namespace,
> and document its purpose with eclassdoc format. Be more verbose
> on the exact problem being solved; remove URL to old upstream bug
> tracker that no l
On śro, 2017-05-10 at 16:08 +0200, Michał Górny wrote:
> Hi, everyone.
>
> Here's a quick batch of improvements to python_moduleinto() in
> python-utils-r1.eclass. Patches are, in order:
>
> 1. fix leftover doc comment,
>
> 2. clarify the doc wrt use across mult
On śro, 2017-05-10 at 20:53 +0200, Michał Górny wrote:
> Allow two special values in the implementation patterns for
> _python_impl_matches(): -2 to indicate all Python 2-compatible
> implementations, and -3 to indicate all Python 3-compatible
> implementations. Both of thos
lmost 6700 ebuilds. I am trying *hard* to commit
changes in large patchsets to reduce cache updates. Of course it is all
pointless if a random Mike Frysinger, developer on special rights, goes
ahead and commits whatever he wants to whatever eclasses he wants to
commit to, whatever time he pleases.
On śro, 2017-05-17 at 21:44 -0700, Daniel Campbell wrote:
> On Sat, May 13, 2017 at 09:32:46AM +0200, Michał Górny wrote:
> > On pią, 2017-05-12 at 17:42 -0700, Daniel Campbell wrote:
> > > On 05/11/2017 12:51 AM, Michał Górny wrote:
> > > > In fact, I'm pers
gin case, I
need to create the necessary logic in the eclass.
>
>On Thu, May 18, 2017 at 12:10 PM, Michał Górny
>wrote:
>
>> On śro, 2017-05-17 at 21:44 -0700, Daniel Campbell wrote:
>> > On Sat, May 13, 2017 at 09:32:46AM +0200, Michał Górny wrote:
>> > >
# Michał Górny (18 May 2017)
# Last release in 2007, upstream disappeared. Requires a lot
# of patching. Unmaintained since 2012. Bad ebuild quality, #514850.
# Does not build anymore, #612398. Removal in 30 days.
app-admin/geolizer
--
Best regards,
Michał Górny
signature.asc
Description
rds?
While I am certainly interested maintaining this package as part of
LLVM, I would really prefer to *know* that I'm maintaining it rather
than learning from a third person that I happen to be the maintainer
even though I haven't even seen the package once.
> +
> + vap...@
On czw, 2017-05-18 at 15:07 -0700, Daniel Campbell wrote:
> On Fri, May 12, 2017 at 08:32:53PM +0200, Michał Górny wrote:
> > On czw, 2017-05-11 at 11:47 +0700, Alex Turbov wrote:
> > > DEPEND=( doc?
> > > || (
> > > (
> &g
you
should have made that clear.
I should also point out that the steps you've taken (and listed in this
mail) are not really relevant. They make you look like a sloppy
maintainer, and a bad Gentoo developer at the best -- and I doubt anyone
would connect removing proxy-maint team with a necessity
*'
}
Note that flags used PYTHON_COMPAT form (with '_') while setup functions
used EPYTHON form (with '.'). Now both are equally happy with both
forms.
--
Best regards,
Michał Górny
---
eclass/python-any-r1.eclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/eclass/python-any-r1.eclass b/eclass/python-any-r1.eclass
index 69f7bb736d22..e4d2d46bc706 100644
--- a/eclass/python-any-r1.eclass
+++ b/eclass/python-any-r1.eclass
@@ -224,7 +224,7 @@ python_gen_a
Update the missed occurence of pattern matching with the new framework.
---
eclass/distutils-r1.eclass | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/eclass/distutils-r1.eclass b/eclass/distutils-r1.eclass
index 1376326c9579..6078fb6d52b7 100644
--- a/eclass
Make the pattern matching code in _python_impl_matches() more lax,
allowing (accidental) mixing of PYTHON_COMPAT-style values with
EPYTHON-style values. This is trivial to do, and solves the problem
introduced by complexity-by-limitation of other eclasses -- where
patterns for dependency strings ar
---
eclass/python-r1.eclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index 8de0a851856c..809dc5f2b8e5 100644
--- a/eclass/python-r1.eclass
+++ b/eclass/python-r1.eclass
@@ -614,6 +614,7 @@ python_parallel_foreach_impl() {
# Example:
#
The function was (verbosely) deprecated in Dec 2014, and banned since
EAPI 6. It is no longer used by any ebuild in ::gentoo.
---
eclass/python-r1.eclass | 35 ---
1 file changed, 35 deletions(-)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index
The variable was deprecated and the warning put in place in Dec 2014. It
is no longer used in any ebuild in ::gentoo.
---
eclass/distutils-r1.eclass | 9 -
1 file changed, 9 deletions(-)
diff --git a/eclass/distutils-r1.eclass b/eclass/distutils-r1.eclass
index 6078fb6d52b7..e79f86bab12d
Rewrite the python_*_all() phase running code to reuse python_setup
instead of hacking on top of python_foreach_impl. The resulting code
is a bit simpler but most importantly, it avoids duplication of code
from python-r1 and ensures that distutils-r1 common phases are directly
altered by changes in
701 - 800 of 7473 matches
Mail list logo
