-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/11/2012 04:25 PM, Michał Górny wrote:
Committed onto vcs-snapshot.eclass after fixing all in-tree users.
Thanks for the update.
One suggestion:
Have you thought about using bsdtar from app-arch/libarchive instead
of GNU ones? You'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- From the eclass:
# XXX: check whether the directory structure inside is
# fine? i.e. if the tarball has actually a parent dir.
This should work with gnu and bsd tar, and sed+sort+wc from
sys-apps/coreutils as well as busybox.
[
On Tue, 12 Jun 2012 15:09:54 +0200
Michael Weber x...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/11/2012 04:25 PM, Michał Górny wrote:
Committed onto vcs-snapshot.eclass after fixing all in-tree users.
Thanks for the update.
One suggestion:
Have
On Tue, 12 Jun 2012 15:26:58 +0200
Michael Weber x...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- From the eclass:
# XXX: check whether the directory structure inside is
# fine? i.e. if the tarball has actually a parent dir.
This should work with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/12 06:49 PM, Brian Harring wrote:
On Sun, Jun 10, 2012 at 01:25:55PM +0100, Ciaran McCreesh wrote:
On Sat, 09 Jun 2012 13:55:53 -0700 Zac Medico
zmed...@gentoo.org wrote:
A dependency atom will have optional SLOT and ABI_SLOT parts.
Hi,
these days still FFLAGS and FCFLAGS are unset by default.
Any objections to to default to CFLAGS of the profile equally to CXXFLAGS?
Thanks justin
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/12/2012 06:55 PM, Justin wrote:
Hi,
these days still FFLAGS and FCFLAGS are unset by default. Any
objections to to default to CFLAGS of the profile equally to
CXXFLAGS?
Thanks justin
This is the first time I see these variables.
On 12.06.2012 21:30, Markos Chandras wrote:
On 06/12/2012 06:55 PM, Justin wrote:
Hi,
these days still FFLAGS and FCFLAGS are unset by default. Any
objections to to default to CFLAGS of the profile equally to
CXXFLAGS?
Thanks justin
This is the first time I see these variables.
# Both have been merged into =dev-python/shiboken-1.1.1.
# Removal in 30 days.
dev-python/apiextractor
dev-python/generatorrunner
signature.asc
Description: This is a digitally signed message part.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/12/2012 04:46 PM, Michał Górny wrote:
Well, I was hoping to come up with something which doesn't involve
running additional 'tar -t', to be honest. I have to think about
it some more time.
FTR,
filelist=$(tar xvC /tmp/xxx
i've noticed a growing trend where people put setup of variables into
pkg_setup that only matter to src_* funcs presumably so they don't have to
call the respective src_* func from an inherited eclass. unfortunately this
adds pointless overhead to binpkgs. can we please move away from this
On Tuesday 12 June 2012 13:55:45 Justin wrote:
these days still FFLAGS and FCFLAGS are unset by default.
Any objections to to default to CFLAGS of the profile equally to CXXFLAGS?
sounds fine
-mike
signature.asc
Description: This is a digitally signed message part.
Calling use in global scope isn't allowed so what are you suggesting
they do instead?
On Tue, Jun 12, 2012 at 11:02 PM, Mike Frysinger vap...@gentoo.org wrote:
i've noticed a growing trend where people put setup of variables into
pkg_setup that only matter to src_* funcs presumably so they
On 2012-06-12 Tue 20:20, Michael Sterrett wrote:
Calling use in global scope isn't allowed so what are you suggesting
they do instead?
Can't they just do something similar to how most cmake-utils and
autotools-utils users do things? For example:
src_configure() {
G2CONF=${G2CONF}
On Tuesday 12 June 2012 23:20:53 Michael Sterrett wrote:
Calling use in global scope isn't allowed so what are you suggesting
they do instead?
as implied in the body of my message, put it into the relevant src_* func. in
this case, src_prepare.
-mike
signature.asc
Description: This is a
On Tuesday 12 June 2012 23:54:45 Mike Frysinger wrote:
On Tuesday 12 June 2012 23:20:53 Michael Sterrett wrote:
Calling use in global scope isn't allowed so what are you suggesting
they do instead?
as implied in the body of my message, put it into the relevant src_* func.
in this case,
Automatically strip trailing newlines from the ChangeLog, and be
better about not adding them in the first place (still not perfect,
but getting there).
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
pym/portage/tests/repoman/test_echangelog.py |9 +
pym/repoman/utilities.py
On 06/12/2012 03:13 PM, Mike Frysinger wrote:
There are edge cases where repoman's changelog code is not as good as
the existing echangelog. Mostly related to out of date headers. Have
the code check the header in more cases not just for missing lines, but
also outdated values all the time.
On 06/12/2012 03:13 PM, Mike Frysinger wrote:
Automatically strip trailing newlines from the ChangeLog, and be
better about not adding them in the first place (still not perfect,
but getting there).
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
19 matches
Mail list logo
