This adds support for using a binary package's compression header to
determine the compression type, providing forward-compatibility for
xz and gzip decompression. The file name extension is disregared, so
that it will be possible use a compression-independent file naming
scheme in the future (see
On 01/15/2015 07:00 PM, Brian Dolbec wrote:
On Thu, 15 Jan 2015 17:27:23 -0800
Zac Medico zmed...@gentoo.org wrote:
# Add -q to bzip2 opts, in order to avoid trailing
garbage after # EOF ignored warning messages due to xpak trailer.
+if comp == bzip2:
+
On Thu, 15 Jan 2015 20:53:02 -0800
Zac Medico zmed...@gentoo.org wrote:
On 01/15/2015 07:00 PM, Brian Dolbec wrote:
On Thu, 15 Jan 2015 17:27:23 -0800
Zac Medico zmed...@gentoo.org wrote:
# Add -q to bzip2 opts, in order to avoid
trailing garbage after # EOF ignored warning
On Wed, 14 Jan 2015 21:59:37 +0100
Andreas K. Huettel dilfri...@gentoo.org wrote:
That said, long time ago I was taught that instruction set
use-flags should be avoided as much as possible. I don't remember
the source for that anymore.
Question to all, is that documented anywhere, and what
03.01.2015 00:53, Mike Pagano пишет:
On Saturday, January 03, 2015 12:39:39 AM Mikle Kolyada wrote:
02.01.2015 20:25, Mike Pagano пишет:
This is in no way complaining about how long it takes to stabilize a
kernel.
As for this fact.
hat type=arch teams developer
The main problem is that:
Christopher Head ch...@chead.ca wrote:
All that requires is knowing the names, though; it would be
fine if no package actually uses the feature yet.
++
More precisely: When changing the names anyway,
IMHO it would be a very good idea to follow the convention of the
flag names in /proc/cpuinfo
Il 15/01/2015 11:30, Alexis Ballier ha scritto:
On Thu, 15 Jan 2015 10:20:15 + (UTC)
Martin Vaeth mar...@mvath.de wrote:
Christopher Head ch...@chead.ca wrote:
All that requires is knowing the names, though; it would be
fine if no package actually uses the feature yet.
++
More
On Thu, 15 Jan 2015 11:50:25 +0100
viv...@gmail.com viv...@gmail.com wrote:
Il 15/01/2015 11:30, Alexis Ballier ha scritto:
On Thu, 15 Jan 2015 10:20:15 + (UTC)
Martin Vaeth mar...@mvath.de wrote:
Christopher Head ch...@chead.ca wrote:
All that requires is knowing the names,
On Thu, 15 Jan 2015 10:20:15 + (UTC)
Martin Vaeth mar...@mvath.de wrote:
Christopher Head ch...@chead.ca wrote:
All that requires is knowing the names, though; it would be
fine if no package actually uses the feature yet.
++
More precisely: When changing the names anyway,
IMHO
On Thu, Jan 15, 2015 at 3:31 AM, Sergey Popov pinkb...@gentoo.org wrote:
So, i like your idea to stick stable to the LTS kernel. While it can
lead to potential problems with some external modules(which are, for
example, marked stable now but does not support 3.4 kernel) the majority
of really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/15/2015 11:01 AM, Rich Freeman wrote:
On Thu, Jan 15, 2015 at 3:31 AM, Sergey Popov pinkb...@gentoo.org
wrote:
So, i like your idea to stick stable to the LTS kernel. While it
can lead to potential problems with some external modules(which
Alexis Ballier aball...@gentoo.org wrote:
More precisely: When changing the names anyway,
IMHO it would be a very good idea to follow the convention of the
flag names in /proc/cpuinfo and add all flags supported
there as possible USE-flags, no matter, whether they are currently
used in
On Thu, 15 Jan 2015 12:03:27 + (UTC)
Martin Vaeth mar...@mvath.de wrote:
Alexis Ballier aball...@gentoo.org wrote:
More precisely: When changing the names anyway,
IMHO it would be a very good idea to follow the convention of
the flag names in /proc/cpuinfo and add all flags
13 matches
Mail list logo
