On 16 Jan 2018 23:32, Mike Gilbert wrote:
> On Tue, Jan 16, 2018 at 4:46 PM, Mike Frysinger wrote:
> > Some ebuilds are a bit hard to fix their use of the network in src
> > phases, so allow them to disable things. This allows us to turn off
> > access by default and for th
From: Mike Frysinger
Some ebuilds are a bit hard to fix their use of the network in src
phases, so allow them to disable things. This allows us to turn off
access by default and for the vast majority while we work out how to
fix the few broken packages.
URL: https://crbug.com/731905
---
man
From: Mike Frysinger
Some ebuilds are a bit hard to fix their use of the network in src
phases, so allow them to disable things. This allows us to turn off
access by default and for the vast majority while we work out how to
fix the few broken packages.
URL: https://crbug.com/731905
---
man
---
v2
- add more sites
- check the trailing URL to filter false positives
repoman/pym/repoman/modules/scan/ebuild/checks.py | 22 ++
repoman/pym/repoman/modules/scan/ebuild/errors.py | 2 ++
repoman/pym/repoman/qa_data.py| 4 +++-
3 files
Running the repoman program locally is a bit unreliable in its
detection. Add a dedicated repoman.git program for people to
run directly if they want.
---
repoman/.repoman_not_installed | 0
repoman/bin/repoman | 10 --
repoman/bin/repoman.git | 37 ++
---
repoman/pym/repoman/modules/scan/ebuild/checks.py | 17 +
repoman/pym/repoman/modules/scan/ebuild/errors.py | 2 ++
repoman/pym/repoman/qa_data.py| 4 +++-
3 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/repoman/pym/repoman/modules/scan/ebui
On 04 Jan 2016 19:17, Brian Dolbec wrote:
> I immediately want to say REJECT!, REJECT!, REJECT!,...
> ...
> I would much prefer you re-base your patch on the rewrite code.
reject != delay ... i don't mind waiting and rebasing
-mike
signature.asc
Description: Digital signature
Some packages list the same atom multiple times (e.g. behind diff USE
flags). If one of them throws an error, we end up listing it more than
once, and the output can get verbose/useless.
---
pym/repoman/scanner.py | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/
On 24 Nov 2015 15:41, Joakim Tjernlund wrote:
> Emerging on my embedded gentoo ppc target I see this:
>
> dev-lang/python-exec-2.0.1-r1::x-portage
> sys-apps/install-xattr-0.5::x-portage
> sys-libs/timezone-data-2015f::x-portage
>
> Where does the name x-portage come from? I do not ha
On 24 Nov 2015 15:58, Zac Medico wrote:
> On 11/24/2015 03:11 PM, Mike Frysinger wrote:
> > This does not support fowners just yet as we'll need to queue/dequeue
> > the accounts on the fly.
> >
> > X-Gentoo-Bug: 566614
> > X-Gentoo-Bug-URL: https://b
This does not support fowners just yet as we'll need to queue/dequeue
the accounts on the fly.
X-Gentoo-Bug: 566614
X-Gentoo-Bug-URL: https://bugs.gentoo.org/566614
---
man/make.conf.5| 4
pym/portage/const.py | 1 +
pym/portage/package/ebuild/conf
On 12 Nov 2015 21:07, Tim Harder wrote:
> On 2015-11-11 14:42, Zac Medico wrote:
> > Please unset all new internal function inside bin/save-ebuild-env.sh.
> > Note that it already uses this line to unset functions beginning with
> > ___eapi:
> >
> >unset -f $(compgen -A function ___eapi_)
> >
>
Since the __* (two) namespace is reserved, and ___* (three) has rarely
(if ever) been used in ebuilds, we can nuke all funcs/vars that start
with that. It makes clean up easier for us.
---
bin/save-ebuild-env.sh | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/bin/save-ebuil
On 12 Nov 2015 16:58, Zac Medico wrote:
> On 11/12/2015 04:06 PM, Mike Frysinger wrote:
> > from ebuilds/eclasses that have already stopped using __:
> > __do_sed_fix ()
> > ___ECLASS_RECUR_MULTILIB=yes
> > ___ECLASS_RECUR_TOOLCHAIN_FUNCS=yes
>
These are internal funcs that should not be exported into the env.
---
bin/save-ebuild-env.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/bin/save-ebuild-env.sh b/bin/save-ebuild-env.sh
index 8036342..31c2d60 100644
--- a/bin/save-ebuild-env.sh
+++ b/bin/save-ebuild-env.sh
@@ -76,6 +76,7 @
On 11 Nov 2015 22:40, Zac Medico wrote:
> On 11/11/2015 10:33 PM, Zac Medico wrote:
> > On 11/11/2015 01:11 PM, Mike Frysinger wrote:
> >> On 11 Nov 2015 13:04, Zac Medico wrote:
> >>> On 11/11/2015 12:55 PM, Mike Frysinger wrote:
> >>>> On 11 Nov 2
On 11 Nov 2015 13:04, Zac Medico wrote:
> On 11/11/2015 12:55 PM, Mike Frysinger wrote:
> > On 11 Nov 2015 11:42, Zac Medico wrote:
> >> On 11/10/2015 08:39 PM, Mike Frysinger wrote:
> >>> +# Set up the bash version compatibility level.
> >>> +__check_b
To try and provide better stability across bash versions,
set the language compat level based on the current EAPI.
This does not ban newer features, it tells bash to use
the older bash behavior when the behavior changes across
versions.
---
bin/eapi.sh| 8
bin/ebuild.sh
On 11 Nov 2015 11:42, Zac Medico wrote:
> On 11/10/2015 08:39 PM, Mike Frysinger wrote:
> > +# Set up the bash version compatibility level.
> > +__check_bash_version() {
>
> Please unset all new internal function inside bin/save-ebuild-env.sh.
> Note that it already
On 11 Nov 2015 10:32, Michał Górny wrote:
> I'm not convinced we ought to do this for EAPI < 6. It is a breaking
> change after all, and as such changes the behavior of EAPI < 6 ebuilds.
that is a false statement. anything not working with bash-3.2 is already
broken according to the PMS.
> There
On 11 Nov 2015 07:33, Ulrich Mueller wrote:
> >>>>> On Tue, 10 Nov 2015, Mike Frysinger wrote:
> > + # Set the compat level in case things change with newer ones. We must
> > not
> > + # export this into the env otherwise we might break other shell
&
To try and provide better stability across bash versions,
set the language compat level based on the current EAPI.
---
bin/eapi.sh | 8
bin/ebuild.sh | 39 +++
2 files changed, 47 insertions(+)
diff --git a/bin/eapi.sh b/bin/eapi.sh
index 528e6f2..b
On 01 Nov 2015 09:36, Zac Medico wrote:
> On 10/31/2015 10:23 PM, Mike Frysinger wrote:
> > The current code implements a lot of ad-hoc argument parsing when it
> > could simply let the argparse module do it all for it. This makes the
> > code easier to understand and
The current code implements a lot of ad-hoc argument parsing when it
could simply let the argparse module do it all for it. This makes the
code easier to understand and extend in the process.
---
bin/xpak-helper.py | 68 --
1 file changed, 25 in
A lot of unittests currently leak content in /tmp when they run.
Rather than explicitly track down every failing test (which we can
do regardless of this), have the runtest runner create a global
tempdir and use that as a base for children tests. Then when the
runtest script finishes, it takes car
A lot of unittests currently leak content in /tmp when they run.
Rather than explicitly track down every failing test (which we can
do regardless of this), have the runtest runner create a global
tempdir and use that as a base for children tests. Then when the
runtest script finishes, it takes car
We don't support python 2.6 anymore, so drop the non-argparse logic.
---
bin/chpathtool.py | 45 +++--
1 file changed, 11 insertions(+), 34 deletions(-)
diff --git a/bin/chpathtool.py b/bin/chpathtool.py
index 842f1f4..73c7a5f 100755
--- a/bin/chpathtool.py
Since we don't support python 2.6 anymore, there's no need to wrap
argparse, so switch all the users to the standard library for it.
---
bin/binhost-snapshot | 4 ++--
bin/ebuild | 4 ++--
bin/egencache| 4 ++--
bin/fixpackages
On 22 Oct 2015 12:54, Paul Varner wrote:
> Mike, I know you're busy with other stuff, but if you ever want to see a
> new gentoolkit/gentoolkit-dev release, consider this your authorization
> to just do it. The README.dev files state how to make releases.
thanks, i think this will help a lot
> S
On 22 Oct 2015 00:45, Mike Frysinger wrote:
> On 21 Oct 2015 16:35, Paul Varner wrote:
> > On 10/20/2015 03:34 AM, Alexander Berntsen wrote:
> > > On 15/10/15 19:42, Paul Varner wrote:
> > > > Over the last couple of days, I have done the following:
> > >
On 21 Oct 2015 16:35, Paul Varner wrote:
> On 10/20/2015 03:34 AM, Alexander Berntsen wrote:
> > On 15/10/15 19:42, Paul Varner wrote:
> > > Over the last couple of days, I have done the following:
> >
> > > 1. Migrated the gentoolkit-dev branch to its own gentoolkit-dev.git
> > > repository
> > >
On 30 May 2015 16:59, Mike Frysinger wrote:
> Rather than each module implementing its own shim around the various
> methods for accessing extended attributes, start a dedicated module
> that exports a consistent API.
noticed i still hadn't pushed this, so i've done so now
i
On 11 Jun 2015 00:21, Brian Dolbec wrote:
> On Sat, 30 May 2015 10:36:05 -0400 Mike Frysinger wrote:
> > so if we're happy with this implementation, i'll start a thread on
> > gentoo-dev so people aren't caught by surprise, and we can merge this
> > for the nex
pushed now
-mike
signature.asc
Description: Digital signature
On 10 Jun 2015 11:54, Zac Medico wrote:
> On 05/30/2015 01:59 PM, Mike Frysinger wrote:
> LGTM, except this one line is indented with spaces instead of tabs in
> vartree.py:
>
> > def tar_contents(contents, root, tar, protect=None, onProgress=None,
&
On 30 May 2015 16:59, Mike Frysinger wrote:
> Rather than each module implementing its own shim around the various
> methods for accessing extended attributes, start a dedicated module
> that exports a consistent API.
ping ... are people ok with this change in API ?
-mike
sign
Rather than hardcode a full path everywhere as a fallback, assume the
value is always set to the right location. The current path isn't the
right place anymore already.
If it turns out we want to support this scenario, we can do it via a
bunch of bootstrapping (and symlinked) files.
---
bin/ebui
On 30 May 2015 12:30, Brian Dolbec wrote:
> On Sat, 30 May 2015 14:27:25 -0400 Mike Frysinger wrote:
> > > > +def get_python_executable(ver):
> > > > + """Find the right python executable for |ver|"""
> > >
On 01 Jun 2015 11:49, Zac Medico wrote:
> On 06/01/2015 10:25 AM, Mike Frysinger wrote:
> > (a) just throw an error and exit when PORTAGE_BIN_PATH is not set ...
> > considering the current portage code points to a path where it is no longer
> > installed, maybe that'
On 02 Jun 2015 16:49, Alexander Berntsen wrote:
> On 02/06/15 16:43, Mike Frysinger wrote:
> > but yeah, I don't see a problem in dropping them
> > yeah especially since gkeys is not 3.2 capable
> > and I'm starting to integrate it in portage
> > those
On 12 Mar 2015 13:52, Duncan wrote:
> Tho as proposed, that all-options section may /optionally/ be moved into
> its own manpage, with an explicit note to that effect in the main
> manpage.
i think splitting the content between two man pages is a pretty bad idea.
would be kind of easy to get dup
On 02 Jun 2015 06:49, Alexander Berntsen wrote:
> On 02/06/15 06:42, Mike Frysinger wrote:
> > the portage ebuild dropped support:
> > python 3.1: 21 months ago
> > python 2.6: 10 months ago
> > python 3.2: 8 weeks ago
> >
> > the python team itself n
On 01 Jun 2015 23:16, Alexander Berntsen wrote:
> On 30/05/15 16:58, Mike Frysinger wrote:
> > We no longer support these in the ebuild and don't want to waste
> > time implementing compatibility shims for them.
>
> In principle I don't mind this at all.
>
&g
On 01 Jun 2015 14:01, Tim Harder wrote:
> On 2015-06-01 13:25, Mike Frysinger wrote:
> > (d) some other alternative ?
>
> If you're sticking with bash, there is also pkgcore's approach of using
> a custom shebang script that handles initialization and related gene
On 01 Jun 2015 02:34, Mike Frysinger wrote:
> -source "${PORTAGE_BIN_PATH:-/usr/lib/portage/bin}"/isolated-functions.sh
> +if [[ -z ${PORTAGE_BIN_PATH} ]] ; then
> + PORTAGE_BIN_PATH=$(dirname "$(dirname "$(readlink -f "$0")")")
> +fi
> +
Rather than hardcode /usr/lib/portage/bin everywhere, use the currently
active script name to locate the right path.
This helps out the Prefix project as they currently rewrite these on the
fly, but even the latest portage no longer installs into that path.
---
bin/ebuild-helpers/die
On 31 May 2015 11:43, Zac Medico wrote:
> In LinkageMapELF.py, there's a fallback mapping for
> multilib categories, which is used by the LinkMapElf class when
> NEEDED.ELF.2 does not contain multilib categories due to being
> generated by older portage. This mapping should be consistent with
> the
On 05 Apr 2015 22:02, Brian Dolbec wrote:
> On Sat, 4 Apr 2015 23:31:25 -0700 Zac Medico wrote:
> > The old http uri redirects to the new https uri, so use the new https
> > uri directly.
> >
> > X-Gentoo-Bug: 469888
> > X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=469888
> > ---
> >
Rather than each module implementing its own shim around the various
methods for accessing extended attributes, start a dedicated module
that exports a consistent API.
---
v4
- merge in recent quickpkg changes
- add a XATTRS_WORKS symbol for easy testing
- use - with -m when
On 30 May 2015 11:14, Mike Frysinger wrote:
> Rather than each module implementing its own shim around the various
> methods for accessing extended attributes, start a dedicated module
> that exports a consistent API.
and it looks like i just missed the new pym/portage/util/xattr.py mod
On 30 May 2015 12:21, Zac Medico wrote:
> On 05/30/2015 08:14 AM, Mike Frysinger wrote:
> > + @classmethod
> > + def list(cls, item, nofollow=False, namespace=None, _names_only=True):
> > + cmd = ['getfattr', '-d', '--absolute-names&
On 30 May 2015 14:42, Mike Gilbert wrote:
> On Sat, May 30, 2015 at 1:18 PM, Brian Dolbec wrote:
> > On Sat, 30 May 2015 12:29:14 -0400 Mike Frysinger wrote:
> >> +from __future__ import print_function
> >
> > If I'm not mistaken, this is not needed for 2.7
On 30 May 2015 11:22, Zac Medico wrote:
> On 05/30/2015 07:36 AM, Mike Frysinger wrote:
> > On 26 May 2015 08:58, Zac Medico wrote:
> >> On 05/26/2015 07:24 AM, Mike Frysinger wrote:
> >>> + # Only check on 32-bit systems. Filtering by $ARCH here isn't perfect
On 30 May 2015 10:18, Brian Dolbec wrote:
> On Sat, 30 May 2015 12:29:14 -0400 Mike Frysinger wrote:
> > +from __future__ import print_function
>
> If I'm not mistaken, this is not needed for 2.7+ anymore. It is
> still for 2.6 though.
i believe you're mistaken :
The bash was getting ugly, and this allows us to add more smarts sanely
to the main script.
---
DEVELOPING | 2 +-
runtests| 156
runtests.sh | 109 --
3 files changed, 157 insertions(+), 11
Rather than each module implementing its own shim around the various
methods for accessing extended attributes, start a dedicated module
that exports a consistent API.
---
bin/xattr-helper.py | 11 +-
pym/portage/tests/util/test_xattr.py | 178
pym/po
We no longer support these in the ebuild and don't want to waste time
implementing compatibility shims for them.
---
.travis.yml | 2 --
DEVELOPING | 8
README | 2 +-
runtests.sh | 4 ++--
4 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/.travis.yml b/.travis.yml
inde
On 26 May 2015 08:58, Zac Medico wrote:
> On 05/26/2015 07:24 AM, Mike Frysinger wrote:
> > + # Only check on 32-bit systems. Filtering by $ARCH here isn't perfect,
> > but
> > + # it should be good enough for our needs.
> > + case ${ARCH
From: Mike Frysinger
Start issuing QA warnings when ELFs are installed using the old 32bit
file interface. These programs can fail out right:
* working with large files (more than 2GiB) can return EOVERFLOW
* stating files on large filesystems w/64bit inodes can fail too
It also can lead to
From: Mike Frysinger
Start issuing QA warnings when ELFs are installed using the old 32bit
file interface. This programs can fail when working with large files
(like ones more than 4GiB), but even just trying to stat a file that
happens to have a 64bit inode. It also can lead to silent
On 14 May 2015 19:01, Mike Frysinger wrote:
> On 14 May 2015 11:43, Brian Dolbec wrote:
> > On Thu, 14 May 2015 06:50:42 -0400 Mike Frysinger wrote:
> > > The repo name is considered missing if there is no explicit
> > > "repo_name" file. But if it's set
On 14 May 2015 11:43, Brian Dolbec wrote:
> On Thu, 14 May 2015 06:50:42 -0400 Mike Frysinger wrote:
> > The repo name is considered missing if there is no explicit
> > "repo_name" file. But if it's set in layout.conf via repo-name, we
> > can skip that. Otherw
From: Bertrand Simonnet
The repo name is considered missing if there is no explicit "repo_name"
file. But if it's set in layout.conf via repo-name, we can skip that.
Otherwise we end up with copy & paste spew.
---
pym/portage/repository/config.py | 1 +
1 file changed, 1 insertion(+)
diff --gi
From: Bertrand SIMONNET
SIGCONT signals should not interrupt any system calls (locking or wait pid for
example).
URL: http://crbug.com/417800
X-Gentoo-Bug-URL: https://bugs.gentoo.org/500436
---
pym/_emerge/Scheduler.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/pym/_emerge/Scheduler.p
On Wednesday, February 05, 2014 03:03:10 Mike Frysinger wrote:
> On Saturday, February 01, 2014 20:38:05 Arfrever wrote:
> > If this attribute is not set explicitly, then it defaults to value of
> > 'masters' attribute.
>
> this i'm not so sure about. wh
On Wednesday, February 05, 2014 19:11:12 Sebastian Luther wrote:
> Am 05.02.2014 09:03, schrieb Mike Frysinger:
> > On Saturday, February 01, 2014 20:38:05 Arfrever Frehtes Taifersar
> > Arahesis wrote:
> >
> > this i'm not so sure about. when you have a local ove
On Wednesday, February 05, 2014 20:57:24 Arfrever wrote:
> Calling portageq multiple times would be too slow for some tools.
i think this is the fundamental point you're trying to side step/ignore.
we've done work in the past to mitigate this. e.g. `portageq envvar -v`
allows you to list multi
etend output.
Acked-by: Mike Frysinger
-mike
signature.asc
Description: This is a digitally signed message part.
On Sunday, February 16, 2014 20:57:29 David James wrote:
> On Fri, Feb 14, 2014 at 1:37 PM, Sebastian Luther wrote:
> > Am 14.02.2014 21:43, schrieb David James:
> > > Uploaded here: https://chromium-review.googlesource.com/#/c/186651/
> > >
> > > You should be able to cherry-pick using this comma
On Friday, February 14, 2014 09:31:19 David James wrote:
> The --newrepo flag tells emerge to recompile a package if it is now being
> pulled from a different repository.
>
> BUG=chromium:200417
> TEST=Verify ebuilds get pulled in when repo changes.
> ---
> man/emerge.1 |
lgtm
-mike
signature.asc
Description: This is a digitally signed message part.
On Monday, February 10, 2014 20:22:36 Chris Reffett wrote:
> This patch adds a --output-style option to repoman, which gives the user
> a choice of output formats for the repoman checks. Choices are "default"
> (current style) and "column" (a greppable format), but it should be easy
> to add more.
On Saturday, February 01, 2014 21:08:11 Arfrever Frehtes Taifersar Arahesis
wrote:
> bin/isolated-functions.sh contains at least 1 useful function, which could
> be exposed for external consumers (without __ prefix), but must have
> private name (with __ prefix) when bin/isolated-functions.sh is u
On Saturday, February 01, 2014 20:38:05 Arfrever Frehtes Taifersar Arahesis
wrote:
> Suggested behavior:
> - Support for new 'updates-masters' attribute in metadata/layout.conf.
makes sense
> If this attribute is not set explicitly, then it defaults to value of
> 'masters' attribute.
this i'm
On Sunday, January 26, 2014 17:53:44 Anthony G. Basile wrote:
> 1) I'm not 100% sure how to do that.
we'll have to (re-)introduce support for building C files. shouldn't be too
hard to start a new directory to hold all the C code. and a simple Makefile
to build them all. i think the tbz2tool.
On Monday, January 27, 2014 15:02:30 viv...@gmail.com wrote:
> patch install from coreutils (and then upstream changes) is not an option?
that route is being pursued independently. we already have a wrapper and will
have one for the foreseeable future.
-mike
signature.asc
Description: This is a
Committed as obvious.
---
man/ebuild.5 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 32c3ea6..89bd6a2 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -1003,6 +1003,9 @@ fi
.fi
.RE
.TP
+.B usev\fR \fI
+Like \fBuse\fR, but also echoes \fIUSE item\fR when
On Wednesday 22 January 2014 16:22:35 Michael Orlitzky wrote:
> I WTF'ed on this for a long time before I noticed that the docs for
> "has" were sort-of contained in "hasv". Might as well give "has" its own.
please use `git send-email` when posting patches
this duplicates the hasv section which i
On Wednesday 22 January 2014 11:10:16 W. Trevor King wrote:
> On Wed, Jan 22, 2014 at 12:35:13AM -0500, Mike Frysinger wrote:
> > On Sunday 19 January 2014 22:26:06 W. Trevor King wrote:
> > > W. Trevor King (4):
> > > pym/portage/package/
On Sunday 19 January 2014 22:26:06 W. Trevor King wrote:
> W. Trevor King (4):
> pym/portage/package/ebuild/fetch.py: Factor out
> _get_checksum_failure_max_tries
> pym/portage/package/ebuild/fetch.py: Factor out _get_fetch_resume_size
> pym/portage/package/ebuild/fetch.py: Factor out _ge
On Sunday 19 January 2014 17:46:36 Alec Warner wrote:
> On Sun, Jan 19, 2014 at 2:45 PM, Alexander Berntsen wrote:
> > On 19/01/14 22:22, Sebastian Luther wrote:
> > > The usual doc string style used in portage is:
> > >
> > > """ text """
> > >
> > > Please use that for new functions. Also make
On Thursday 21 March 2013 20:17:30 Mike Frysinger wrote:
> On Thursday 21 March 2013 19:25:08 James Cloos wrote:
> > >>>>> "MF" == Mike Frysinger writes:
> > MF> realistically, there are no man pages that are under 4k. look at the
> > MF> ref
Acked-by: Mike Frysinger
-mike
signature.asc
Description: This is a digitally signed message part.
On Monday 20 January 2014 23:00:31 Chris Reffett wrote:
> + if not ro_filesystems:
> + return ro_filesystems
> +
> + for directory in dir_list:
> + for filesystem in ro_filesystems:
> + if filesystem == directory:
> + r
On Monday 20 January 2014 22:53:25 Gordon Pettey wrote:
> If your going to make that argumint, ewe mite a's well right the
> documentation in LOL-1337. Encouraging bad grammar in documentation just
> make's thing's harder for everybody.
(1) don't top post
(2) you posted nothing to support your ass
On Monday 20 January 2014 19:50:54 Chris Reffett wrote:
> + # Check for read-only filesystems
please use full sentences. that means putting a period at the end. this
applies to many additions in this patch.
> + try:
> + with io.open("/proc/mounts", mode='r',
encodi
On Sunday 19 January 2014 05:39:25 Alexander Berntsen wrote:
> On 19/01/14 10:17, Mike Frysinger wrote:
> > prefer OSes -> OS's
>
> That's just not proper English.
i don't think that phrase means what you think it means. if you're wishing
for English to be
On Monday 20 January 2014 06:05:30 Sebastian Luther wrote:
> Currently layout.conf is not under PMS control. This basically means
> that every PM (or version thereof) may support different keys and assign
> different meanings to them. Portage's behavior for unknown keys in
> layout.conf is to ignor
On Monday 20 January 2014 01:02:31 Alec Warner wrote:
> Are you still doing crazy crap like disabling all of the portage locking?
> ;p
yes & no. we make sure we hold the right locks and don't do operations that
otherwise cause problems. then we disable the core lock grabbing :P.
the current lo
On Sunday 19 January 2014 11:59:36 Mike Gilbert wrote:
> On Sun, Jan 19, 2014 at 4:44 AM, Mike Frysinger wrote:
> > Chromium OS for a long time was restricted to EAPI 4 for two reasons --
> > it had an old portage version (and upgrading to a newer one regressed
> > performa
On Sunday 19 January 2014 05:48:33 Alexander Berntsen wrote:
> On 19/01/14 10:20, Mike Frysinger wrote:
> > typically when we delete/rename an option, we give users a heads
> > up. that means a cycle where the old option exists but emits a
> > warning before switching to the
On Tuesday 14 January 2014 16:15:48 Tom Wijsman wrote:
> On Mon, 13 Jan 2014 23:59:11 -0500 Mike Frysinger wrote:
> > we probably should just use dev branches in the main repo, at least
> > for people who have write access to the repo
> >
> > dev/$USERNAME/
>
On Friday 17 January 2014 18:03:57 Tom Wijsman wrote:
> ---
please shorten your commit summary and move more content to the body
> +getNonSystemArchiveDepends.archivers = {
it is super weird to attach to the object like this. some might even say
wrong. move it into the class definition.
def
btw, suggestion for commit summary/message:
repoman: deprecate G2CONF
Deprecate the G2CONF variable as requested by the GNOME team.
URL: http://bugs.gentoo.org/482084
-mike
signature.asc
Description: This is a digitally signed message part.
On Wednesday 15 January 2014 19:07:20 Tom Wijsman wrote:
> +class DeprecateG2CONF(LineCheck):
> + repoman_check_name = 'G2CONF.deprecated'
> + re = re.compile(r'.*G2CONF.*')
> +
> + def check(self, num, line):
> + """Run the check on line and return error if there is one"""
Acked-by: Mike Frysinger
btw you should keep the patch summary short. if it goes long, better to move
it to the main body.
-mike
signature.asc
Description: This is a digitally signed message part.
On Saturday 18 January 2014 19:21:11 Alexander Berntsen wrote:
> Rename --autounmask-write to --autounmask.
typically when we delete/rename an option, we give users a heads up. that
means a cycle where the old option exists but emits a warning before switching
to the new one. then we can delet
On Saturday 18 January 2014 21:00:48 Chris Reffett wrote:
> --- /dev/null
> +++ b/pym/portage/util/rochecker.py
> @@ -0,0 +1,81 @@
> +#-*- coding:utf-8 -*-
> +# Copyright 2014 Gentoo Foundation
> +# Distributed under the terms of the GNU General Public License v2
> +"""
> +Methods to check whether
On Tuesday 14 January 2014 21:58:38 Tom Wijsman wrote:
> On Sun, 05 Jan 2014 15:42:48 -0800 Brian Dolbec wrote:
> > 2) start working on a solution,
> >a) if you have significant progress, but need more time, mark it
> > accordingly, assign it to yourself, leave a comment, etc.
>
> Assign
On Saturday 18 January 2014 17:57:38 Tom Wijsman wrote:
> On Sat, 18 Jan 2014 08:43:12 -0800 "W. Trevor King" wrote:
> > On Sat, Jan 18, 2014 at 04:02:02PM +0100, Tom Wijsman wrote:
> > I think the idea is that you shouldn't need to refer to an external
> > resource like the mailing list to underst
1 - 100 of 315 matches
Mail list logo
