Thomas D. posted on Sat, 04 Apr 2015 22:09:36 +0200 as excerpted:
Title: New net-firewall/shorewall all-in-one package
$ echo New net-firewall/shorewall all-in-one package | wc -c
46
The glep says the title must be 44 chars, max. You're over by a couple
chars.
Abbreviating package to pkg
TL;DR: (1) Please consider either making Documentation a top-level-menu
link (preferable), or at least change Support to Support and
Documentation. (2) On the documentation lander page, add a one big
list link to a browser-keyword-searchable list of docs, like the old
docs project page had.
On Fri, Apr 03, 2015 at 01:59:25AM +0200, Hanno Böck wrote:
Tricky thing here, because then you'd need to rename the libs. E.g.
libssl to liblibressl or something.
But then every program with a build environment to link to libssl would
first have to be patched to link to our specialized
On Fri, Apr 03, 2015 at 01:31:53PM +0200, hasufell wrote:
Not anymore. We will go for libressl USE flag for the same reason
there is a libav USE flag now (working subslots etc).
Um, ok. That still only allows one or the other to be installed though,
right? So if you want a package that only
Brian Dolbec posted on Fri, 03 Apr 2015 06:31:27 -0700 as excerpted:
On Fri, 3 Apr 2015 11:52:39 + (UTC)
Duncan 1i5t5.dun...@cox.net wrote:
Brian Dolbec posted on Thu, 02 Apr 2015 23:59:06 -0700 as excerpted:
enalyze is little known to users.
I'd never heard of enalyze before
On 04/02/2015 09:32 AM, Rich Freeman wrote:
Out of curiosity, what is keeping us from having USE flag dependencies
handled dynamically, in the same way that package dependencies are?
If portage can figure out that I need libxml2 installed even if I
don't put it in /var/lib/portage/world, why
On 04/04/2015 09:42 PM, Duncan wrote:
TL;DR: (1) Please consider either making Documentation a top-level-menu
link (preferable), or at least change Support to Support and
Documentation. (2) On the documentation lander page, add a one big
list link to a browser-keyword-searchable list of
On Sat, 4 Apr 2015, Michał Górny wrote:
The problem
---
Package moves (and slot moves) are currently a three part process:
1. committing the package under the new name (slot), and removing
the old files,
Actually, you shouldn't remove the old package at this point because
it
Dnia 2015-04-04, o godz. 20:14:21
Ulrich Mueller u...@gentoo.org napisał(a):
On Sat, 4 Apr 2015, Michał Górny wrote:
The problem
---
Package moves (and slot moves) are currently a three part process:
1. committing the package under the new name (slot), and removing
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the bikesheds again ... (smile)
--
,,
SUPPORT ___//___, Philip Webb
On 04/04/2015 02:41 PM, Philip Webb wrote:
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the bikesheds again ... (smile)
This is consistent with a lot of other stuff. For example, emacs is
Dnia 2015-04-04, o godz. 13:47:47
Alex Brandt alund...@gentoo.org napisał(a):
On Saturday, April 04, 2015 14:41:37 Philip Webb wrote:
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the
On Saturday, April 04, 2015 14:41:37 Philip Webb wrote:
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the bikesheds again ... (smile)
I don't disagree but will simply point out that if this
Hello, everyone.
I'd like to suggest extending the pkgmove (slotmove) action code
a little bit to reduce the amount of issues hit by users during
the transition period following package moves. Please read on
and let me know what you think.
The problem
---
Package moves (and slot moves)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/04/2015 01:09 PM, Thomas D. wrote:
Hi,
some of you maybe know or already have noticed that the
net-firewall/shorewall* ebuilds were re-integrated into a new
all-in-one ebuild for easier maintenance.
The package is proxy-maintained.
On Sat, 4 Apr 2015, Michał Górny wrote:
This is not true for slotmoves. The previous slot can be reused by
versions not matching the dependency spec of the move. One can even
move some versions to a new slot, while leaving others in the old
one.
For example, you could have
Dnia 2015-04-04, o godz. 21:36:37
Ulrich Mueller u...@gentoo.org napisał(a):
On Sat, 4 Apr 2015, Michał Górny wrote:
This is not true for slotmoves. The previous slot can be reused by
versions not matching the dependency spec of the move. One can even
move some versions to a new slot,
On Sat, Apr 4, 2015 at 1:49 PM, Michał Górny mgo...@gentoo.org wrote:
Dnia 2015-04-04, o godz. 13:47:47
Alex Brandt alund...@gentoo.org napisał(a):
I don't disagree but will simply point out that if this becomes true, we
should also move dev-lang/python to dev-python, dev-lang/ruby to
150404 Alex Brandt wrote:
On Saturday, April 04, 2015 14:41:37 Philip Webb wrote:
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the bikesheds again ... (smile)
I don't disagree but will simply
Hi,
some of you maybe know or already have noticed that the
net-firewall/shorewall* ebuilds were re-integrated into a new all-in-one
ebuild for easier maintenance.
The package is proxy-maintained.
While preparing the new ebuild I discussed with the proxy-maint team and
shorewall users if we
On Sat, 4 Apr 2015, Philip Webb wrote:
150404 Alex Brandt wrote:
On Saturday, April 04, 2015 14:41:37 Philip Webb wrote:
I read the recent thread re the new app-eselect.
Doing my weekly system update,
it strikes me that 'eselect' itself sb there too.
Time to paint the bikesheds again ...
21 matches
Mail list logo
