W dniu 11.05.2014 23:27, Pacho Ramos pisze:
> El dom, 11-05-2014 a las 19:46 +0200, Michał Górny escribió:
>> Hello, developers.
>>
>> I'd like to raise the following item for discussion: making .xz
>> the default compressor used by portage for documentation, man pages
>> and info files. That is, t
On Sun, 11 May 2014 19:46:50 +0200
Michał Górny wrote:
> Rationale: xz-utils is quite widespread nowadays and it is a part
> of @system set. It can achieve better compression ratio than bzip2,
> and faster decompression at the same time.
Some thoughts:
What about putting multiple doc / man / in
On Mon, 12 May 2014 00:47:17 -0600
Ryan Hill wrote:
> > 1. cgroup -- puts all processes spawned by ebuild to cgroup, and
> > kills all of them once phase exits (prevents leaving orphans),
> >
> > 2. ipc-sandbox -- puts all processes spawned by ebuild to a separate
> > IPC namespace, preventing t
On Mon, 12 May 2014 11:31:45 +0200
Marcin Mirosław wrote:
> Imho there is no real advantages to change current compressor for man
> files.
It's insufficient to experiment on a single file to make such claim,
you may very well found a file that works equally well with multiple
compression algorit
В Sun, 11 May 2014 18:26:32 -0500
Gordon Pettey пишет:
> A lot of small files (e.g. AUTHORS, ChangeLog
>
> FWIW: On my system, I have 59M of bz2 files in /usr/share/man and
> /usr/share/doc. A short script to decompress those and recompress with xz
> -6e reduced that to 36M.
Very strange o_O
В Mon, 12 May 2014 14:47:36 +0400
Alexander Tsoy пишет:
> В Sun, 11 May 2014 18:26:32 -0500
> Gordon Pettey пишет:
>
> > A lot of small files (e.g. AUTHORS, ChangeLog
> >
> > FWIW: On my system, I have 59M of bz2 files in /usr/share/man and
> > /usr/share/doc. A short script to decompress thos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- -1 from me until Portage is capable of detecting if the user's
operating system supports the FEATUREs, and informing them of this.
I also agree with Ryan that the relevant Linux options should be added
to the Gentoo Linux menu.
- --
Alexander
ber
On Mon, 12 May 2014 14:47:36 +0400
Alexander Tsoy wrote:
> Here is my test results. xz options: "--lzma2=preset=6e,dict=4MiB".
> Larger dictionary size does not improve compression ratio, I get
> even worse results with just "-6e" or "-9e". man-bz2 is a full copy of
> my /usr/share/man, man-xz is
В Mon, 12 May 2014 14:17:11 +0200
Tom Wijsman пишет:
> On Mon, 12 May 2014 14:47:36 +0400
> Alexander Tsoy wrote:
>
> > Here is my test results. xz options: "--lzma2=preset=6e,dict=4MiB".
> > Larger dictionary size does not improve compression ratio, I get
> > even worse results with just "-6e"
Am Montag, 12. Mai 2014, 13:15:35 schrieb Alexander Berntsen:
> -1 from me until Portage is capable of detecting if the user's
> operating system supports the FEATUREs, and informing them of this.
>
> I also agree with Ryan that the relevant Linux options should be added
> to the Gentoo Linux menu
On Mon, May 12, 2014 at 8:59 AM, Andreas K. Huettel
wrote:
> Am Montag, 12. Mai 2014, 13:15:35 schrieb Alexander Berntsen:
>> -1 from me until Portage is capable of detecting if the user's
>> operating system supports the FEATUREs, and informing them of this.
>>
>> I also agree with Ryan that the
On Mon, 12 May 2014 13:15:35 +0200
Alexander Berntsen wrote:
> - -1 from me until Portage is capable of detecting if the user's
> operating system supports the FEATUREs, and informing them of this.
A flag being present or not in FEATURES does not mean anything, and if
you're assuming that it does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/05/14 17:23, Ciaran McCreesh wrote:
> A flag being present or not in FEATURES does not mean anything, and
> if you're assuming that it does then you have a bug.
Please try to stay on topic, and don't obfuscate your posts
needlessly. Note that I
On Mon, 12 May 2014 17:46:57 +0200
Alexander Berntsen wrote:
> On 12/05/14 17:23, Ciaran McCreesh wrote:
> > A flag being present or not in FEATURES does not mean anything, and
> > if you're assuming that it does then you have a bug.
> Please try to stay on topic, and don't obfuscate your posts
>
On 12/05/14 18:56, Julian Ospald (hasufell) wrote:
> hasufell14/05/12 15:56:05
>
> Added:libsdl2-2.0.3-static-libs.patch
> Log:
> version bump
>
> (Portage version: 2.2.10/cvs/Linux x86_64, signed Manifest commit with key
> BDEED020)
>
> Revision ChangesPath
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/2014 05:42 PM, Michał Górny wrote:
> Hi, everyone.
>
> Almost 9 months ago I've committed three new FEATURES for portage:
> cgroup, ipc-sandbox and network-sandbox. Today I'd like to propose
> enabling at least the latter two by default.
>
>
On Mon, May 12, 2014 at 12:07 PM, Rick "Zero_Chaos" Farina
wrote:
> What about talking to local network resources? In my metasploit ebuild
> it has tests available which talk to a local database and are perfectly
> safe, however, if postgresql is started on the system the tests don't
> work, the
On Mon, May 12, 2014 at 11:59 AM, Ciaran McCreesh
wrote:
> On Mon, 12 May 2014 17:46:57 +0200
> Alexander Berntsen wrote:
>> On 12/05/14 17:23, Ciaran McCreesh wrote:
>> > A flag being present or not in FEATURES does not mean anything, and
>> > if you're assuming that it does then you have a bug.
On Mon, 12 May 2014 12:44:38 -0400
Mike Gilbert wrote:
> On Mon, May 12, 2014 at 11:59 AM, Ciaran McCreesh
> wrote:
> > On Mon, 12 May 2014 17:46:57 +0200
> > Alexander Berntsen wrote:
> >> On 12/05/14 17:23, Ciaran McCreesh wrote:
> >> > A flag being present or not in FEATURES does not mean any
On Mon, May 12, 2014 at 12:46 PM, Ciaran McCreesh
wrote:
> On Mon, 12 May 2014 12:44:38 -0400
> Mike Gilbert wrote:
>> On Mon, May 12, 2014 at 11:59 AM, Ciaran McCreesh
>> wrote:
>> > On Mon, 12 May 2014 17:46:57 +0200
>> > Alexander Berntsen wrote:
>> >> On 12/05/14 17:23, Ciaran McCreesh wrot
Mike Gilbert wrote:
> On Mon, May 12, 2014 at 12:46 PM, Ciaran McCreesh
> wrote:
> > Why, though?
>
> We should probably emit an error message advising the user to enable
> the kernel option or disable the network-sandbox feature. This should
> happen when we call unshare() and that fails with e
Dnia 2014-05-12, o godz. 12:40:42
Rich Freeman napisał(a):
> However, I don't know if portage actually makes the network namespace
> that it creates useful - I don't know if it contains any interfaces,
> or if they are initialized/etc.
It sets up a private loopback (alike 'ifconfig lo up') that
Dnia 2014-05-12, o godz. 12:07:11
"Rick \"Zero_Chaos\" Farina" napisał(a):
> What about talking to local network resources? In my metasploit ebuild
> it has tests available which talk to a local database and are perfectly
> safe, however, if postgresql is started on the system the tests don't
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2014 01:08 PM, Michał Górny wrote:
> Dnia 2014-05-12, o godz. 12:07:11
> "Rick \"Zero_Chaos\" Farina" napisał(a):
>
>> What about talking to local network resources? In my metasploit ebuild
>> it has tests available which talk to a local da
Dnia 2014-05-12, o godz. 13:22:20
"Rick \"Zero_Chaos\" Farina" napisał(a):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/12/2014 01:08 PM, Michał Górny wrote:
> > Dnia 2014-05-12, o godz. 12:07:11
> > "Rick \"Zero_Chaos\" Farina" napisał(a):
> >
> >> What about talking to local n
On Mon, 12 May 2014 18:59:33 +0300
Samuli Suominen wrote:
> > - $(LIBTOOL) --mode=link $(CC) -o $@ $(OBJECTS)
> > $(VERSION_OBJECTS) $(LDFLAGS) $(EXTRA_LDFLAGS) $(LT_LDFLAGS)
> > + $(LIBTOOL) --mode=link $(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS)
> > $(EXTRA_LDFLAGS) $(LT_LDFLAGS)
>
> You know that
Rich Freeman wrote:
> > Longterm, this makes it year after year more difficult to develop
> > software for "Linux".
>
> I'm with you here, but what is the solution?
>
> If we say we stick to upstream then we don't provide pkg-config files
> at all (in these cases).
I think this is a sane default
On Mon, May 12, 2014 at 1:22 PM, Rick "Zero_Chaos" Farina
wrote:
> That would be nice, can we do the network namespaces so that I at least
> don't have to bind to a random port? That alone would be a major
> improvement in usability.
>From my very limited understanding of network namespaces, when
On 12/05/14 20:47, Peter Stuge wrote:
> Rich Freeman wrote:
>>> Longterm, this makes it year after year more difficult to develop
>>> software for "Linux".
>> I'm with you here, but what is the solution?
>>
>> If we say we stick to upstream then we don't provide pkg-config files
>> at all (in thes
Dnia 2014-05-12, o godz. 21:24:26
Samuli Suominen napisał(a):
> On 12/05/14 20:47, Peter Stuge wrote:
> > Rich Freeman wrote:
> >>> Longterm, this makes it year after year more difficult to develop
> >>> software for "Linux".
> >> I'm with you here, but what is the solution?
> >>
> >> If we s
Samuli Suominen wrote:
> >> If we say we stick to upstream then we don't provide pkg-config files
> >> at all (in these cases).
>
> > I think this is a sane default.
>
> Except having pkg-config is the only way to fix some of the build
> issues we are seeing today, like getting 'Libs.private: ' f
On Mon, May 12, 2014 at 9:48 PM, Peter Stuge wrote:
> Samuli Suominen wrote:
>> >> If we say we stick to upstream then we don't provide pkg-config files
>> >> at all (in these cases).
>>
>> > I think this is a sane default.
>>
>> Except having pkg-config is the only way to fix some of the build
>>
On Mon, 12 May 2014 20:48:16 +0200
Peter Stuge wrote:
> Samuli Suominen wrote:
> > Except having pkg-config is the only way to fix some of the build
> > issues we are seeing today, like getting 'Libs.private: ' for
> > static linking, there has been multiple bugs lately,
>
> I honestly don't th
Tom Wijsman wrote:
> besides a temporary fix downstream it should go upstream;
I think there is agreement that this is the ideal, and that the
discussion is about what to do when that seems out of reach.
> > My key point is that it isn't Gentoo's responsibility or duty to fix
> > problems introd
On 12/05/14 22:25, Peter Stuge wrote:
(Are we seriously discussing banning something useful as pkg-config
files?! That's retarded. Must be some joke.)
>>> I don't think I said to ban them. I said that I want Gentoo to stay
>>> close to upstream by default. I also said that maintainers sh
Samuli Suominen:
> You know that adding $(LDFLAGS) so late in the linker line makes whole
> -Wl,--as-needed get ignored?
>
Yes I know and the patch is correct as is.
On 05/12/2014 06:47 PM, Peter Stuge wrote:
> Rich Freeman wrote:
>>> Longterm, this makes it year after year more difficult to develop
>>> software for "Linux".
>>
>> I'm with you here, but what is the solution?
>>
>> If we say we stick to upstream then we don't provide pkg-config files
>> at all (
Hi Ben,
On 05/12/2014 07:06 AM, Ben de Groot wrote:
> On 12 May 2014 03:28, Jauhien Piatlicki wrote:
>> Hi all,
>>
>> LXQt 0.7.0 has been released [1].
>>
>> As it is project different from LXDE
>
> That is debatable. LXQt is released by the merged LXDE and Razor-Qt
> upstreams. One could say th
Samuli Suominen:
>
> On 12/05/14 20:47, Peter Stuge wrote:
>> Rich Freeman wrote:
Longterm, this makes it year after year more difficult to develop
software for "Linux".
>>> I'm with you here, but what is the solution?
>>>
>>> If we say we stick to upstream then we don't provide pkg-conf
On Mon, 12 May 2014 21:25:55 +0200
Peter Stuge wrote:
> Tom Wijsman wrote:
> > besides a temporary fix downstream it should go upstream;
>
> I think there is agreement that this is the ideal, and that the
> discussion is about what to do when that seems out of reach.
Yes, I think that's the cas
On Mon, 12 May 2014 23:43:34 +0200
Tom Wijsman wrote:
> Yeah, it's tricky; this makes me think, can't we perhaps install them
> in a separate directory that pkg-config could check?
A quick collective brainstorm on IRC gives the idea that this is not
worth the effort, as this imposes patching mul
On Mon, May 12, 2014 at 5:47 AM, Alexander Tsoy wrote:
> В Sun, 11 May 2014 18:26:32 -0500
> Gordon Pettey пишет:
>
> > A lot of small files (e.g. AUTHORS, ChangeLog
> >
> > FWIW: On my system, I have 59M of bz2 files in /usr/share/man and
> > /usr/share/doc. A short script to decompress those a
On Mon, 12 May 2014 11:39:10 +0200
Tom Wijsman wrote:
> On Mon, 12 May 2014 00:47:17 -0600
> Ryan Hill wrote:
>
> > > 1. cgroup -- puts all processes spawned by ebuild to cgroup, and
> > > kills all of them once phase exits (prevents leaving orphans),
> > >
> > > 2. ipc-sandbox -- puts all pro
Hi,
I do not know if this came up... glibc must be bumped first[1].
Alon
[1] https://bugs.gentoo.org/show_bug.cgi?id=504032
On Mon, 12 May 2014 11:35:00 +0200 Tom Wijsman wrote:
> On Sun, 11 May 2014 19:46:50 +0200
> Michał Górny wrote:
>
> > Rationale: xz-utils is quite widespread nowadays and it is a
> > part of @system set. It can achieve better compression ratio
> > than bzip2, and faster decompression at the same
On 05/12/2014 01:17 PM, Markos Chandras wrote:
> It's only me who spoke on behalf of LXDE so far :( gtk2 is still
> alive, and lxde said that while it's still alive, the GTK lxde will
> still be supported. After all, lxde-base, as the name implies, is for
> lxde-related packages (maintained by lxde
Hello,
On Mon, 12 May 2014 14:47:36 +0400 Alexander Tsoy wrote:
> В Sun, 11 May 2014 18:26:32 -0500
> Gordon Pettey пишет:
>
> > A lot of small files (e.g. AUTHORS, ChangeLog
> >
> > FWIW: On my system, I have 59M of bz2 files in /usr/share/man and
> > /usr/share/doc. A short script to decompre
Hello,
On Sun, 11 May 2014 23:42:38 +0200 Michał Górny wrote:
> Hi, everyone.
>
> Almost 9 months ago I've committed three new FEATURES for portage:
> cgroup, ipc-sandbox and network-sandbox. Today I'd like to propose
> enabling at least the latter two by default.
>
>
> Firstly, I'd like to sho
> On Tue, 13 May 2014, Andrew Savchenko wrote:
> Please consider that by default du shows block size, not byte size.
> Than means that if file is actually 1234 bytes large, without -b it
> will be still accounted for 4096 bytes on 4K-block filesystem.
This raises another question, namely if f
49 matches
Mail list logo
