Hi,
I just installed fresh system on my pc, selected
'default/linux/x86/10.0/desktop' profile and noticed ldap among
default USE flags. Why is that needed? I suppose there are more users
w/o ldap auth on desktops than with it.
So my proposal is to remove it from
profiles/targets/desktop/make.defaults. Any objections?
05-05-2012, 05:10 PM
Alec Warner
RFC: remove ldap from desktop profiles use flags
On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov <maksbotan@gentoo.org> wrote:
> Hi,
> I just installed fresh system on my pc, selected
> 'default/linux/x86/10.0/desktop' profile and noticed ldap among
> default USE flags. Why is that needed? I suppose there are more users
> w/o ldap auth on desktops than with it.
> So my proposal is to remove it from
> profiles/targets/desktop/make.defaults. Any objections?
>
So how are you going to avoid destroying machines that rely on it
being on by default?
-A
05-05-2012, 05:12 PM
Samuli Suominen
RFC: remove ldap from desktop profiles use flags
On 05/05/2012 08:10 PM, Alec Warner wrote:
On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov<maksbotan@gentoo.org> wrote:
Hi,
I just installed fresh system on my pc, selected
'default/linux/x86/10.0/desktop' profile and noticed ldap among
default USE flags. Why is that needed? I suppose there are more users
w/o ldap auth on desktops than with it.
So my proposal is to remove it from
profiles/targets/desktop/make.defaults. Any objections?
So how are you going to avoid destroying machines that rely on it
being on by default?
-A
An answer to the "But, it has always been like this." is a matter of
issuing a portage news item (glep 42)
(But yeah, I agree we need to be careful with changing the USE flags set
globally by profiles)
05-05-2012, 05:18 PM
Maxim Koltsov
RFC: remove ldap from desktop profiles use flags
2012/5/5 Alec Warner <antarus@gentoo.org>:
> On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov <maksbotan@gentoo.org> wrote:
>> Hi,
>> I just installed fresh system on my pc, selected
>> 'default/linux/x86/10.0/desktop' profile and noticed ldap among
>> default USE flags. Why is that needed? I suppose there are more users
>> w/o ldap auth on desktops than with it.
>> So my proposal is to remove it from
>> profiles/targets/desktop/make.defaults. Any objections?
>>
>
> So how are you going to avoid destroying machines that rely on it
> being on by default?
Well, i just haven't thought about that. Maybe make news item or
something of this kind. But now when i see this simple removal implies
such consequences, i think i can just live with it, disabling manually
> -A
>
05-05-2012, 06:34 PM
Mike Frysinger
RFC: remove ldap from desktop profiles use flags
On Saturday 05 May 2012 13:10:10 Alec Warner wrote:
> On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov wrote:
> > I just installed fresh system on my pc, selected
> > 'default/linux/x86/10.0/desktop' profile and noticed ldap among
> > default USE flags. Why is that needed? I suppose there are more users
> > w/o ldap auth on desktops than with it.
> > So my proposal is to remove it from
> > profiles/targets/desktop/make.defaults. Any objections?
>
> So how are you going to avoid destroying machines that rely on it
> being on by default?
move it from the desktop/ subdir to the versioned trees like 10.0/ and
2008.0/, and eventually when we create a 11.0/, it'll no longer be the
default.
-mike
05-05-2012, 07:12 PM
Markos Chandras
RFC: remove ldap from desktop profiles use flags
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 05/05/2012 06:10 PM, Alec Warner wrote:
> On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov
> <maksbotan@gentoo.org> wrote:
>> Hi, I just installed fresh system on my pc, selected
>> 'default/linux/x86/10.0/desktop' profile and noticed ldap among
>> default USE flags. Why is that needed? I suppose there are more
>> users w/o ldap auth on desktops than with it. So my proposal is
>> to remove it from profiles/targets/desktop/make.defaults. Any
>> objections?
>>
>
> So how are you going to avoid destroying machines that rely on it
> being on by default?
>
> -A
>
Users will note the use flag change when they run "emerge -uDN world"
and they will add it to their make.conf. I am also in favor of
dropping ldap from the desktop profiles.
Jesus Rivero (Neurogeek) wrote:
>
> On May 5, 2012 3:14 PM, "Markos Chandras" <hwoarang@gentoo.org
> <mailto:hwoarang@gentoo.org>> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 05/05/2012 06:10 PM, Alec Warner wrote:
>> > On Sat, May 5, 2012 at 5:31 PM, Maxim Koltsov
>> > <maksbotan@gentoo.org <mailto:maksbotan@gentoo.org>> wrote:
>> >> Hi, I just installed fresh system on my pc, selected
>> >> 'default/linux/x86/10.0/desktop' profile and noticed ldap among
>> >> default USE flags. Why is that needed? I suppose there are more
>> >> users w/o ldap auth on desktops than with it. So my proposal is
>> >> to remove it from profiles/targets/desktop/make.defaults. Any
>> >> objections?
>> >>
>> >
>> > So how are you going to avoid destroying machines that rely on it
>> > being on by default?
>> >
>> > -A
>> >
>> Users will note the use flag change when they run "emerge -uDN world"
>> and they will add it to their make.conf. I am also in favor of
>> dropping ldap from the desktop profiles.
>
> I don't like this change much. There are valid use cases for an ldap use
> flag in the desktop profile that could break easily with this change.
>
> Also, you could make the same case for adding -ldap to your make.conf
Not to mention, you add the possibility that the user may miss the
change since they are not expecting it. I would expect it when I was
changing profiles but not so much just coming out of the blue.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
05-05-2012, 08:44 PM
Michael Weber
RFC: remove ldap from desktop profiles use flags
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/05/2012 09:55 PM, Dale wrote:
> Not to mention, you add the possibility that the user may miss the
> change since they are not expecting it. I would expect it when I
> was changing profiles but not so much just coming out of the blue.
We should make emerge -v (display USE flags) non-optional.
Users should be trained to recognize the green/red use flag changes.
Do whatever you what, I've set make.conf:USE=ldap on machines relying
on it.
Michael
- --
Gentoo Dev
http://xmw.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
2012/5/5 Michael Weber <xmw@gentoo.org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 05/05/2012 09:55 PM, Dale wrote:
>> Not to mention, you add the possibility that the user may miss the
>> change since they are not expecting it. *I would expect it when I
>> was changing profiles but not so much just coming out of the blue.
>
> We should make emerge -v (display USE flags) non-optional.
> Users should be trained to recognize the green/red use flag changes.
currently portage _does_ show use changed w/o -v, and show _all_ use
w/ -v, please leave it as is -v is way too verbose to see the changes
in a multi-package merge
> Do whatever you what, I've set make.conf:USE=ldap on machines relying
> on it.
> Michael
Mee too, that sum to zero machines tough
Sun May 6 00:30:05 2012
Return-path: <arch-general-bounces@archlinux.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Sun, 06 May 2012 00:22:53 +0300
Received: from gerolde.archlinux.org ([66.211.214.132]:46475)
by s2.java-tips.org with esmtp (Exim 4.77)
(envelope-from <arch-general-bounces@archlinux.org>)
id 1SQmRJ-0005mY-HZ
for tom@linux-archive.org; Sun, 06 May 2012 00:22:53 +0300
Received: from gudrun.archlinux.org (gudrun.archlinux.org [66.211.214.131])
by gerolde.archlinux.org (Postfix) with ESMTP id 4821B9009C;
Sat, 5 May 2012 17:22:33 -0400 (EDT)
Received: from gerolde.archlinux.org (gerolde.archlinux.org [66.211.214.132])
by gudrun.archlinux.org (Postfix) with ESMTP id 5CD5B7004C
for <arch-general@archlinux.org>; Sat, 5 May 2012 17:22:31 -0400 (EDT)
Received-SPF: pass (gmail.com ... _spf.google.com: 209.85.217.172 is
authorized to use 'bo.bjornsen@gmail.com' in 'mfrom' identity (mechanism
'ip4:209.85.128.0/17' matched)) receiver=gerolde.archlinux.org;
identity=mailfrom; envelope-from="bo.bjornsen@gmail.com";
helo=mail-lb0-f172.google.com; client-ip 9.85.217.172
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com
[209.85.217.172])
by gerolde.archlinux.org (Postfix) with ESMTPS id E5BD090087
for <arch-general@archlinux.org>; Sat, 5 May 2012 17:22:30 -0400 (EDT)
Received: by lbbgo11 with SMTP id go11so2540982lbb.3
for <arch-general@archlinux.org>; Sat, 05 May 2012 14:22:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s 120113;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:x-enigmail-version:content-type;
bh=uhqGkkxyxxfab2tjfND//AVZNToo50bz19iAgzpcSQo=;
b=IFXnMT/so00q+PPvBUYnL4v2+kalPOJjjK3V7IJpgcSLK14q9cz615x9C OUD4nlaAj
q7wf80fj2J3q0bZ7WgX/q1wnzyF0qryknGPiGSmtK4dDZiTX5aTERLwGVTEB+Rt/rKoU
8K/wQNNPvj8N31b5yamkZrxNoSnmM69rCiKI3lToEDf8sV2FzvQxi 8NZXRFIN01nElBh
0JJeVP5/lDxn3ttlvZPyuOmFjHfwnnXRsxMeOTxalLbtdCYS+jT2mx5QBI zr/Mvhoj7+
cODp5naVsLXQDaZIqrwuu144K2ZWAK5NaGXvtcFE1dRCq062uw ouRwu5G8iRJNK7SkpW
JuJg=Received: by 10.152.147.33 with SMTP id th1mr1892292lab.9.1336252975093;
Sat, 05 May 2012 14:22:55 -0700 (PDT)
Received: from [192.168.1.3] ([90.149.150.38])
by mx.google.com with ESMTPS id u4sm13533240lad.5.2012.05.05.14.22.53
(version=SSLv3 cipher=OTHER); Sat, 05 May 2012 14:22:53 -0700 (PDT)
Message-ID: <4FA59A27.6070307@gmail.com>
Date: Sat, 05 May 2012 23:22:47 +0200
From: =?ISO-8859-1?Q?Bjørn_Øivind_Bjørnsen? <bo.bjornsen@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:12.0) Gecko/20120425 Thunderbird/12.0
MIME-Version: 1.0
To: arch-general@archlinux.org
References: <CAG-2HqXai1w8iNdPx=u8HLMOMEuS8FQsBw2pGC8V8YASD3Jtww@ma il.gmail.com>
<alpine.LNX.2.00.1205052318070.18062@flfcurer.be t>
In-Reply-To: <alpine.LNX.2.00.1205052318070.18062@flfcurer.be t>
X-Enigmail-Version: 1.4.1
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature";
boundary="------------enig902FC05302882AE211987B5B"
Subject: Re: [arch-general] [HEADSUP] /lib/security/* moving to
/usr/lib/security/
X-BeenThere: arch-general@archlinux.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: General Discussion about Arch Linux <arch-general@archlinux.org>
List-Id: General Discussion about Arch Linux <arch-general.archlinux.org>
List-Unsubscribe: <http://mailman.archlinux.org/mailman/options/arch-general>,
<mailto:arch-general-request@archlinux.org?subject=unsubscribe>
List-Archive: <http://mailman.archlinux.org/pipermail/arch-general>
List-Post: <mailto:arch-general@archlinux.org>
List-Help: <mailto:arch-general-request@archlinux.org?subject=help>
List-Subscribe: <http://mailman.archlinux.org/mailman/listinfo/arch-general>,
<mailto:arch-general-request@archlinux.org?subject=subscribe>
Errors-To: arch-general-bounces@archlinux.org
Sender: arch-general-bounces@archlinux.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig902FC05302882AE211987B5B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 05/05/12 23:19, Adrian C. wrote:
> On Sat, 14 Apr 2012, Tom Gundersen wrote:
>
>> with files in /lib/security to move them to /usr/lib/security.
>
> Hi Tom, I'm curious, does this move have anything to do with systemd?
>
>
This is a part of the /usr move, as discussed previously here:
http://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022625.html