-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/03/12 05:17 PM, Markos Chandras wrote:
> net-misc/wakeonlan
I'll take this one..
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)
iF4EAREIAAYFAk9Q23EACgkQAJxUfCtlWe0SIgD/cnWB5kdzyJfzf5MZnX73aIfQ
GfYKFX047IkboH6bHjQA/iutdhBTfeq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/03/12 10:41 AM, Zac Medico wrote:
> On 03/09/2012 07:21 AM, Michael Orlitzky wrote:
>> The advantage that the eapi function has over a comment is that
>> it's not magic -- it's just normal bash syntax. So we've
>> addressed that issue at a smal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/03/12 02:50 PM, Ulrich Mueller wrote:
>> On Mon, 12 Mar 2012, Ciaran McCreesh wrote:
>> GLEP 55 is simple, it solves all the problems we have (including
>> the version issue, which everyone is conveniently ignoring), it
>> doesn't require u
On 2012-03-12, at 9:22 PM, Joshua Kinard wrote:
>
> And yes, I've already tested out udev-181 on a VM with a
> separate /usr. With devtmpfs, the system fully boots just fine, no
> initramfs needed. Guess what the only piece of software to mess up is?
> Udev. I largely think it's a timing iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/03/12 11:14 PM, Joshua Kinard wrote:
> On 03/12/2012 22:33, Ian Stakenvicius wrote:
>
>>
>> On 2012-03-12, at 9:22 PM, Joshua Kinard
>> wrote:
>>
>>>
>>> And yes, I've already tested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/03/12 10:34 AM, Richard Yao wrote:
> On 03/21/12 10:18, Justin wrote:
>> I will not extract part of the software, e.g. subroutines, for
>> use in other contexts without permission of the author.
>
> Portage could be considered to be one of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/03/12 12:02 PM, Ciaran McCreesh wrote:
> On Fri, 23 Mar 2012 11:58:47 -0400 Mike Gilbert
> wrote:
>>> oasis_src_compile() { oasis_src_compile_no_doc if has doc
>>> ${IUSE} && use doc; then ocaml setup.ml -doc || die fi }
>>
>> This should pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/03/12 12:19 PM, Ciaran McCreesh wrote:
> On Fri, 23 Mar 2012 12:14:39 -0400 Ian Stakenvicius
> wrote:
>> I don't know if I follow this one or not. When inheriting an
>> eclass, all entities within the eclass get me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/03/12 12:32 PM, Ian Stakenvicius wrote:
> On 23/03/12 12:19 PM, Ciaran McCreesh wrote:
>> On Fri, 23 Mar 2012 12:14:39 -0400 Ian Stakenvicius
>> wrote:
>>> I don't know if I follow this one or not. When i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/03/12 04:04 AM, Ian Whyman wrote:
> On 27 March 2012 08:33, Dirkjan Ochtman wrote:
>> On Mon, Mar 26, 2012 at 20:44, Alec Warner
>> wrote:
Long term, we may want to consider porting pybugz to use
Bugzilla's XML-RPC api to avoid such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/03/12 02:47 PM, Rich Freeman wrote:
> On Tue, Mar 27, 2012 at 2:34 PM, Alexandre Rostovtsev
>
>> The partitioning scheme is something that the user needs to
>> decide on *before* getting Gentoo up and running. After the user
>> had finished in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/03/12 03:04 PM, Aaron W. Swenson wrote:
>
>> You know, we have "Code Listing 2.1: Filesystem Example" in
>> Section 4, we could always adjust that to have a /usr/portage
>> partition in it (take a bit of space away from /home, or
>> something)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/03/12 03:05 PM, William Hubbs wrote:
> All,
>
> I know this has come up before, but I don't really recall what the
> specific objections were.
>
> IMO the portage directory doesn't belong under /usr at all. I was
> chatting with another deve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/03/12 04:08 PM, Kent Fredric wrote:
> On 28 March 2012 08:59, William Hubbs wrote:
>> What I was wanting to discuss mainly was that /usr/portage isn't
>> right; I think we need to move that out of the /usr directory.
>>
>> I'm not sure what t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/03/12 03:04 PM, Rich Freeman wrote:
> On Wed, Mar 28, 2012 at 2:53 PM, Christoph Mende
> wrote:
>>
>> I believe it's /var/lib/. Here's what FHS says: /var/cache
>> is intended for cached data from applications. Such data is
>> locally genera
On 2012-04-15, at 5:03 AM, Ryan Hill wrote:
> On Sun, 15 Apr 2012 01:35:40 -0700
> Zac Medico wrote:
>
>> On 04/15/2012 01:16 AM, Ryan Hill wrote:
>>> Right now we have support in some packages for user patches - those being
>>> patches dropped into /etc/portage/patches/pkgname/ - which are a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/04/12 06:03 PM, Andreas K. Huettel wrote:
>
> Dear all,
>
> I'd like to suggest we introduce the following very useful feature,
> as soon as possible (which likely means in the next EAPI?):
>
> * two new files in profile directories supporte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/05/12 03:23 PM, hasufell wrote:
> On 05/20/2012 03:25 PM, Michał Górny wrote:
>> On Sun, 20 May 2012 15:33:11 +0300 Samuli Suominen
>> wrote:
>
>>> ChangeLog entries missing for every autotools.eclass
>>> modification today.
>
>> I will re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/05/12 01:13 PM, Kent Fredric wrote:
> On 25 May 2012 03:02, Ralph Sennhauser wrote:
>> On Thu, 24 May 2012 16:40:02 +0200 Michał Górny
>> wrote:
>>
>>> d) Talk with github folks to add our repo as 'mirror'.
>>
>> Can we keep the master on G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/05/12 03:40 PM, William Hubbs wrote:
> All,
>
> I realize this has been discussed and there are definite opinions
> about which method works well. So, I want to take a different
> approach.
>
> Is there any interest in documenting and support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/05/12 10:56 AM, William Hubbs wrote:
> On Sun, May 27, 2012 at 10:49:07AM -0400, Ian Stakenvicius wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 26/05/12 03:40 PM, William Hubbs wrote:
>>> Al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/05/12 01:01 PM, Michał Górny wrote:
> ... In other words, removing a pager leaves system in a broken
> state. AFAICS, 'eselect pager' doesn't even support a system
> without pager -- it just fails miserably. So the user is either
> forced to in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/06/12 10:07 AM, Ulrich Mueller wrote:
>> On Wed, 06 Jun 2012, Samuli Suominen wrote:
>
>> # Samuli Suominen (06 Jun 2012) #
>> Vulnerable and no longer used by anything in tree wrt #403415 #
>> Removal in 30 days
> Why a version depende
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/06/12 03:00 PM, Pacho Ramos wrote:
> El jue, 07-06-2012 a las 19:44 +0100, Ciaran McCreesh escribió:
>> On Thu, 07 Jun 2012 20:43:54 +0200 Pacho Ramos
>> wrote:
I would prefer, as a workaround, allow reverse deps to
RDEPEND on glib:2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/06/12 03:23 PM, Pacho Ramos wrote:
> El vie, 08-06-2012 a las 12:16 -0700, Zac Medico escribió:
>> It's close enough to ABI_SLOT that it would make more sense just
>> to use ABI_SLOT because it's more flexible.
>
> In that case, I think it's c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/12 08:45 AM, Davide Pesavento wrote:
> On Sun, Jun 10, 2012 at 2:25 PM, Ciaran McCreesh
> wrote:
>> On Sat, 09 Jun 2012 13:55:53 -0700 Zac Medico
>> wrote:
>>> A dependency atom will have optional SLOT and ABI_SLOT parts.
>>> Using the db
-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
>> wrote:
>>> A dependency atom will have optional SLOT and ABI_SLOT parts.
>>> Using the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey all - I'd like to propose that enewuser forces updates to a user's
home dir and shell whenever it is called, so that if this changes with
new versions of an ebuild it is dealt with automatically rather than
having to modify them in pkg_postinst/p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 01:19 PM, Michał Górny wrote:
> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
> wrote:
>
>> + ### force updates of some user properties +
>> usermod -d "${ehome}" "${euser}&qu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:18 PM, Mike Gilbert wrote:
> On 6/13/2012 12:00 PM, Ian Stakenvicius wrote:
>> Hey all - I'd like to propose that enewuser forces updates to a
>> user's home dir and shell whenever it is called, so that if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:09 PM, Fabian Groffen wrote:
> On 13-06-2012 12:00:16 -0400, Ian Stakenvicius wrote:
>> Hey all - I'd like to propose that enewuser forces updates to a
>> user's home dir and shell whenever it is called, s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 01:21 PM, Ian Stakenvicius wrote:
> On 13/06/12 01:19 PM, Michał Górny wrote:
>> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
>> wrote:
>
>>> + ### force updates of some user properties
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 02:45 PM, Ian Stakenvicius wrote:
> On 13/06/12 01:21 PM, Ian Stakenvicius wrote:
>> On 13/06/12 01:19 PM, Michał Górny wrote:
>>> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius
>>> wrote:
>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 03:04 PM, Mike Frysinger wrote:
>
> we have egetshell and egethome already. thus it's fairly easy to
> detect the transition case. if they installed the older version
> which set values that you now want to change: if has_version
> ' e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 03:14 PM, Mike Frysinger wrote:
>
> eset{home,shell} don't exist today, so you should implement them
> :) -mike
RFC - heavily based on enewuser.
- --- user.eclass [some timestamp]
+++ user.eclass.esethome [some other timesta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 04:51 PM, Mike Frysinger wrote:
> On Wednesday 13 June 2012 15:35:40 Ian Stakenvicius wrote:
>> --- user.eclass [some timestamp] +++
>> user.eclass.esethome [some other timestamp] @@ -388,3 +388,63
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/06/12 06:30 PM, Tony "Chainsaw" Vroon wrote:
> Good evening,
>
> As per bug #421037, there is a demand to make multiple voicemail
> storage backends switchable within the ebuild. The USE_EXPAND
> mechanism would automatically provide an explan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/06/12 07:58 PM, Peter Stuge wrote:
> Samuli Suominen wrote:
>> 9'ish consumers. I propose "Enable support for the PostScript
>> language"
>
> Perhaps "ps" or "postscript" instead of the implementation-centric
> "gs" ?
>
>
> //Peter
>
I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/06/12 10:43 PM, Samuli Suominen wrote:
> On 06/15/2012 05:02 AM, Mike Frysinger wrote:
>> On Thursday 14 June 2012 21:16:31 Samuli Suominen wrote:
>>> So how about renaming USE="gs" consumers to USE="ps" and making
>>> USE="ps" global flag with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/06/12 09:27 AM, Peter Stuge wrote:
> Mike Frysinger wrote:
>>> + # lets see if the username already exists + if [[
>>> ! -n $(egetent passwd "${euser}") ]] ; then
>>
>> "! -n" -> "-z"
>
> Does the $() argument ever need to be doub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/06/12 09:37 AM, Pacho Ramos wrote:
> El sáb, 16-06-2012 a las 13:43 +0100, Ciaran McCreesh escribió:
>> On Sat, 16 Jun 2012 14:26:16 +0200 Pacho Ramos
>> wrote:
>>> About suggesting new item (like forcing rebuilding of other
>>> packages as di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/06/12 12:18 PM, Ciaran McCreesh wrote:
> On Sat, 16 Jun 2012 17:24:22 +0200 Peter Stuge
> wrote:
>> Ciaran McCreesh wrote:
Could it work to make automatic signatures of imported ABI,
and simply compare signatures when a provider pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/06/12 12:24 PM, Ciaran McCreesh wrote:
> On Sat, 16 Jun 2012 17:16:34 +0200 Pacho Ramos
> wrote:
>> I can try to check it if no maintainer shows more packages
>> showing this stable API unstable ABIs issues
>
> Please do. This is a fairly im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/06/12 11:53 AM, Michał Górny wrote:
> On Sun, 17 Jun 2012 17:46:00 +0200 Thomas Sachau
> wrote:
>>>
>>> ... If I weren't using 32-bit libs, and now I want to compile
>>> 32-bit wine, I have to recompile most of my libraries for both
>>> ABIs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/06/12 05:33 AM, Richard Yao wrote:
> On 06/21/2012 04:08 AM, Duncan wrote:
>> Richard Yao posted on Wed, 20 Jun 2012 18:16:23 -0400 as
>> excerpted:
>>
>>> 3. How does getting a x86 system to boot differ from getting a
>>> MIPS system or ARM s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/06/12 03:05 PM, David Leverton wrote:
> Michał Górny wrote:
>> Hello,
>>
>> A simple solution to a program long-unsolved. In GLEP form.
>
> Just a couple of minor points/nitpicks:
>
> [ Snip! ]
>
> 2) It's not forbidden for package A to dep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/06/12 08:24 PM, Richard Yao wrote:
> On 06/21/2012 06:51 PM, Rich Freeman wrote:
>> we're a DISTRO - we integrate and ship what upstream gives us...
>
> RHEL is a distribution, but I understand that RedHat does a great
> deal of upstream progr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/06/12 12:48 AM, Zac Medico wrote:
> On 06/21/2012 02:32 PM, David Leverton wrote:
>> Michał Górny wrote:
>>> But in the current form, the spec doesn't allow passing
>>> IUSE_RUNTIME flags to has_version() so we're on the safe side
>>> :P.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/06/12 08:42 PM, Zac Medico wrote:
> On 06/10/2012 11:18 AM, Zac Medico wrote:
>> On 06/10/2012 05:25 AM, Ciaran McCreesh wrote:
>>> On Sat, 09 Jun 2012 13:55:53 -0700 Zac Medico
>>> wrote:
A dependency atom will have optional SLOT and ABI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/06/12 01:58 PM, Zac Medico wrote:
> On 06/25/2012 06:03 AM, Ian Stakenvicius wrote:
>> On 23/06/12 08:42 PM, Zac Medico wrote:
>>> On 06/10/2012 11:18 AM, Zac Medico wrote:
>>>> On 06/10/2012 05:25 AM, Ciaran Mc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/06/12 09:41 PM, Kent Fredric wrote:
> I was doing a fresh Gentoo install today, following the manual, and
> it appeared to me that the manual suggests to install a "logger"
> and a "cron", and gives some defacto suggestions.
>
> However, the a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/06/12 05:30 AM, Zac Medico wrote:
> On 06/30/2012 01:46 AM, Torsten Veller wrote:
>> * Ian Stakenvicius :
>>> FYI, all the work subslotting the perl stuff doesn't work yet,
>>> so it's probably best to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/06/12 11:16 AM, Mike Frysinger wrote:
> On Saturday 30 June 2012 07:22:39 Zac Medico wrote:
>> On 06/30/2012 04:07 AM, Pacho Ramos wrote:
>>> I would like to discuss a bit more issues like:
>>> https://bugs.gentoo.org/show_bug.cgi?id=423087
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/06/12 01:30 PM, Pacho Ramos wrote:
> El sáb, 30-06-2012 a las 13:17 -0400, Ian Stakenvicius escribió:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 30/06/12 11:16 AM, Mike Frysinger wrote:
>>> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey all -- so with Zac's help I've got a script now that will
significantly speed up testing of EAPI=4-slot-abi from my ('axs') overlay.
The script upgrades your system's portage db (/var/db/pkg) so that any
EAPI=4 atoms currently installed will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/07/12 05:05 AM, Kent Fredric wrote:
> On 3 July 2012 20:24, Michał Górny wrote:
>>
>> --depclean?
>
> eix Module-Metadata [I] perl-core/Module-Metadata Available
> versions: ~1.0.3 ~1.0.4 ~1.0.5 1.0.6 ~1.0.9<--- not unmasked
> by --auto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/07/12 07:29 AM, Peter Stuge wrote:
> Zac Medico wrote:
>>> I'd suggest a special ebuild phase to check for ABI
>>> changes, like the pre_pkg_preinst_abi_check phase
>>> suggested here:
>>>
>>> https://bugs.gentoo.org/show_b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/07/12 06:40 AM, Rich Freeman wrote:
> On Wed, Jul 11, 2012 at 4:27 AM, Duncan <1i5t5.dun...@cox.net>
> wrote:
>> Being able to choose not to run systemd at all? If there's no
>> need to build systemd, than what it requires is irrelevant.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/07/12 11:40 PM, Walter Dnes wrote:
> On Wed, Jul 11, 2012 at 09:49:18AM -0400, Michael Mol wrote
>> Walter Dnes (very active over in gentoo-user) has put a lot of
>> work into testing and documenting mdev as an alternative for
>> udev. There's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 12:17 AM, Ben de Groot wrote:
> On 12 July 2012 06:51, Zac Medico wrote:
>>
>> Here's another related bug report, specifically about the solving
>> the libxml2/qt-webkit/chromium conflict:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 01:01 AM, Ben de Groot wrote:
> On 12 July 2012 07:42, William Hubbs wrote:
>> On Wed, Jul 11, 2012 at 10:57:42PM +0200, Diego Elio Pettenò
>> wrote:
>>> Il 11/07/2012 21:11, William Hubbs ha scritto:
I am about to release udev-186-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 03:17 AM, Michał Górny wrote:
> On Thu, 12 Jul 2012 13:01:21 +0800 Ben de Groot
> wrote:
>
>> On 12 July 2012 07:42, William Hubbs
>> wrote:
>>> On Wed, Jul 11, 2012 at 10:57:42PM +0200, Diego Elio Pettenò
>>> wrote:
Il 11/07/2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 07:41 AM, Ben de Groot wrote:
> On 12 July 2012 17:52, Rich Freeman wrote:
>> On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot
>> wrote:
>>> Actually, there is another workable solution, and that is to
>>> set USE="-gstreamer -icu" for qt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 10:19 AM, Michał Górny wrote:
> On Thu, 12 Jul 2012 09:47:33 -0400 Ian Stakenvicius
> wrote:
>> Updating vdb shouldn't be an issue here, as long as pkg_postinst
>> doesn't crash mid-stream. Is th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/07/12 10:20 AM, Michał Górny wrote:
> On Thu, 12 Jul 2012 09:43:57 -0400 Ian Stakenvicius
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 12/07/12 01:01 AM, Ben de Groot wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/07/12 06:16 PM, Zac Medico wrote:
> On 07/15/2012 03:08 PM, Doug Goldstein wrote:
>> Is it valid to do something like:
>>
>> move media-plugins/mytharchive media-plugins/mythplugins move
>> media-plugins/mythbrowser media-plugins/mythplugins m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/07/12 09:00 PM, Maxim Kammerer wrote:
> On Mon, Jul 16, 2012 at 3:30 AM, Duncan <1i5t5.dun...@cox.net>
> wrote:
>> Thinking in that direction does stimulate yet another idea, tho.
>> What about a squashfs root? AFAIK squashfs is read-only at u
On 2012-07-17, at 7:07 PM, Olivier Crête wrote:
> I'm sure most people can't
> even explain the difference between them.
>
/sbin is for bins that only root should be able to run. easy. :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 03:47 PM, Michael Mol wrote:
> On Wed, Jul 18, 2012 at 3:25 PM, Canek Peláez Valdés
> wrote:
>> On Wed, Jul 18, 2012 at 2:18 PM, Michael Mol
>> wrote:
>>
>> The real benefit is that it allows you to mount any partition, if
>> the tools
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 03:49 PM, Peter Stuge wrote:
> William Hubbs wrote:
>> /etc/init.d/foo stop start
>>
>> would no longer work the way you might expect because there would
>> be no way to tell whether start is a command or an argument to
>> stop.
>>
>> W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 03:55 PM, Michael Mol wrote:
> On Wed, Jul 18, 2012 at 3:50 PM, Ian Stakenvicius
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 18/07/12 03:47 PM, Michael Mol wrote:
>>> On We
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 04:05 PM, Alec Warner wrote:
> [...] However lets say I have coreutils in / and coreutils in my
> initramfs. I upgrade coreutils from v1 to v2. Are you saying that
> you are too afraid to update coreutils in / and then also update it
> in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 04:09 PM, William Hubbs wrote:
>
> The other approach, which is on the bug, still has this issue,
> e.g.
>
> /etc/init.d/foo command1 arg1 arg2 command2 arg3 arg4 command3
> arg5
>
> gets pretty ugly pretty quick. which arguments go wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/07/12 06:18 AM, Maxim Kammerer wrote:
> On Fri, Jul 20, 2012 at 11:32 AM, Michael Weber
> wrote:
>> is it intentional behavior, that home directories created by
>> enewuser belong to $user:root (or pwd group) instead of
>> $user:$group ?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/07/12 01:54 PM, Ciaran McCreesh wrote:
> On Fri, 20 Jul 2012 13:43:15 -0400 Alexandre Rostovtsev
> wrote:
>>> If you dep upon foo[linguas_en(+)] and linguas_en isn't in
>>> IUSE, what happens?
>>
>> Fatal error. If a package installs its tran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/07/12 03:13 PM, Ciaran McCreesh wrote:
> On Fri, 20 Jul 2012 15:05:35 -0400 Ian Stakenvicius
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20/07/12 01:54
>> PM, Ciaran McCreesh wrote:
>>> On Fri,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/07/12 03:48 PM, Alexandre Rostovtsev wrote:
> On Fri, 2012-07-20 at 20:17 +0100, Ciaran McCreesh wrote:
>> On Fri, 20 Jul 2012 15:15:31 -0400 Alexandre Rostovtsev
>> wrote:
That's sensitive to old versions ebuilds being removed from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/07/12 09:58 PM, Jorge Manuel B. S. Vicetto wrote:
> On 24-07-2012 01:33, Rich Freeman wrote:
>> On Mon, Jul 23, 2012 at 8:07 PM, Jorge Manuel B. S. Vicetto
>> wrote:
>>>
>>> I propose to commit this news item in 2 or 3 days. Does anyone
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 07:39 AM, Fabian Groffen wrote:
> From a different angle, perhaps stage3s shouldn't include a
> default /etc/make.conf at all. Would solve this issue nicely, and
> doesn't require a news item at all, IMO.
>
Would that work? We still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 02:52 PM, Rick "Zero_Chaos" Farina wrote:
> On 07/24/2012 09:33 AM, Fabian Groffen wrote:
>> On 24-07-2012 09:24:03 -0400, Rich Freeman wrote:
>>> I guess this is a matter of opinion, but on Gentoo I don't
>>> think we're really at much r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 05:13 PM, Brian Harring wrote:
> On Tue, Jul 24, 2012 at 04:32:00PM -0400, Michael Mol wrote:
>>
>> I've often seen cases like these handled by keeping a referenced
>> file where it's traditionally expected to be found, but leaving a
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 08:55 PM, Walter Dnes wrote:
> On Tue, Jul 24, 2012 at 11:42:31AM +0200, Ralph Sennhauser wrote
>
>> man 5 portage about files in /etc/portage
>>
>> make.conf The global custom settings for Portage. See
>> make.conf(5). If present, this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/07/12 10:55 AM, Michael Mol wrote:
> On Tue, Jul 31, 2012 at 10:48 AM, "Paweł Hajdan, Jr."
> wrote:
>> On 7/26/12 8:26 PM, Rich Freeman wrote:
>>> I've been messing around with namespaces and some of what
>>> systemd has been doing with them,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/08/12 02:57 AM, Duncan wrote:
> Jason A. Donenfeld posted on Thu, 09 Aug 2012 06:33:02 +0200 as
> excerpted:
>
> Consider... five years ago was 2007. Android hadn't been released
> yet at this point in 2007 (November, according to the LWN 2007
On 2012-08-17, at 11:00 PM, "Gregory M. Turner" wrote:
> It has come to my attention that gentoo supports "relative" ROOT, which is to
> say that, by design, portage will act as though (in bash terms):
>
> ROOT
>
> equals
>
> "${PWD}/${ROOT}"
>
> when (again in bash terms):
>
> [[ $ROOT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/08/12 03:58 PM, William Hubbs wrote:
> On Fri, Aug 24, 2012 at 01:50:14PM -0400, Alexandre Rostovtsev
> wrote:
>> On Fri, 2012-08-24 at 12:10 -0500, William Hubbs wrote:
>>> The second question this bug brings up is whether services
>>> should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/08/12 07:48 PM, William Hubbs wrote:
> On Sat, Aug 25, 2012 at 07:40:43AM +0900, hero...@gentoo.org
> wrote:
>> Besides, IMHO, we should avoid changing OpenRC's default
>> dependency too often. The solution for one user can be received
>> as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/08/12 11:53 AM, William Hubbs wrote:
> On Sat, Aug 25, 2012 at 03:19:24PM +0900, hero...@gentoo.org
> wrote:
>> If we set rc_provide="net" in rc.conf, the services that need net
>> can be tricked as we intended to.
This makes more sense to me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/08/12 04:16 PM, William Hubbs wrote:
>
> The bottom line here is: I don't think all of the services we have
> set up to "need net" in their default configuration should be set
> up that way. It would make OpenRC work out of the box for many
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/08/12 10:35 AM, Mike Gilbert wrote:
> On Tue, Aug 28, 2012 at 4:06 AM, Michał Górny
> wrote:
>> On Tue, 28 Aug 2012 06:26:02 +0200 Arfrever Frehtes Taifersar
>> Arahesis wrote:
>>
>>> 2012-08-28 00:19:28 Michał Górny napisał(a):
+case $
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/08/12 10:43 AM, Michał Górny wrote:
> On Tue, 28 Aug 2012 10:10:01 +0200 Tiziano Müller
> wrote:
>
>> Am Dienstag, den 28.08.2012, 10:06 +0200 schrieb Michał Górny:
>>> On Tue, 28 Aug 2012 06:26:02 +0200 Arfrever Frehtes Taifersar
>>> Arahesi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/08/12 11:47 AM, Rich Freeman wrote:
> On Tue, Aug 28, 2012 at 11:35 AM, Sylvain Alain
> wrote:
>> Hi everyone, I don't want to start a flamewar on that subject,
>> but I would like to know if there's any official position about
>> the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/08/12 08:37 AM, Michael Mol wrote:
> On Thu, Aug 30, 2012 at 7:29 AM, Johannes Huber
> wrote:
>
> [snip]
>
>>> Developers have only a limited amount of time, and this will
>>> eat into it. The result is likely to not be new shiny ebuilds
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/08/12 08:30 AM, Rich Freeman wrote:
> On Thu, Aug 30, 2012 at 7:29 AM, Johannes Huber
> wrote:
>>
>> EAPI 0 is more readable than EAPI 4? No benefit for maintainer?
>> No benefit for user who wants to read the ebuild? Realy?
>
> Then why mak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/08/12 09:04 AM, Rich Freeman wrote:
> On Thu, Aug 30, 2012 at 8:58 AM, Ian Stakenvicius
> wrote:
>> If you are rewriting a full ebuild as your solution, and the
>> ebuild you start with is EAPI<4 , then Markos would ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/08/12 09:14 AM, Rich Freeman wrote:
> On Thu, Aug 30, 2012 at 9:04 AM, Ian Stakenvicius
> wrote:
>>
>> The primary benefit to the policy that dev's should bump EAPI
>> when bumping ebuilds is so that older inferi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/08/12 10:56 AM, Alexis Ballier wrote:
> Michał Górny wrote:
>>
>> I believe that the more important direction here is to make
>> development *easier*, not harder. Adding the same DEPENDs over
>> and over again to every single package is at l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/08/12 11:27 AM, Alexandre Rostovtsev wrote:
> On Fri, 2012-08-31 at 15:45 +0100, Ciaran McCreesh wrote:
>> On Fri, 31 Aug 2012 10:21:15 +0200 Ulrich Mueller
>> wrote:
>>> Coming back to this old topic [1]. Is there still consensus
>>> that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/08/12 12:08 PM, Ian Stakenvicius wrote:
> On 31/08/12 11:27 AM, Alexandre Rostovtsev wrote:
>> On Fri, 2012-08-31 at 15:45 +0100, Ciaran McCreesh wrote:
>>> On Fri, 31 Aug 2012 10:21:15 +0200 Ulrich Mueller
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/08/12 12:12 PM, Fabian Groffen wrote:
> On 31-08-2012 18:08:12 +0200, Michał Górny wrote:
>> And for a reasonable Gentoo toolchain, pkg-config is a must-have.
>> At least since we deprecated and are seriously fighting libtool.
>
> what?
depre
1 - 100 of 802 matches
Mail list logo
