On 2015-12-18 21:15, Sébastien Luttringer wrote:

On ven., 2015-12-18 at 14:57 -0500, Dave Reisner wrote:

...

On Dec 18, 2015 14:43, "Sébastien Luttringer" wrote: I assume this is a copy paste error... Seems like you're suggesting we use resolved by default? Yes it is, the new hosts line will be: hosts: files resolve mymachines myhostname

Yes too, I'm suggesting to use nss-resolve by default, as it switch to nss-dns for configuration with systemd-resolved disabled.

...

...

2) Merge /usr/local/bin and /usr/local/sbin. This may require user intervention if /usr/local/sbin is not empty. So I'll post an announcement about that. I'm running my system since September with merged sbin with no problem.

Why do we care what people do with /usr/local? Nothing we change here makes our lives easier and only potentially inflicts pain on users who have split between /usr/local/bin and sbin. If we were to change this, I'd suggest we just drop /usr/local/sbin from the package. Pacman will drop tracking of the dir and there won't be any potential need for user interaction.

The idea behind this is to clean our default PATH from the useless difference between sbin and bin.

--- profile (revision 256723) +++ profile (working copy) @@ -4,7 +4,7 @@ umask 022

# Set our default path -PATH="/usr/local/sbin:/usr/local/bin:/usr/bin" +PATH="/usr/local/bin:/usr/bin" export PATH

I'm fine with dropping the symlink, it will be easier and no announcement to write. I did that to not break the path search in that directory. Maybe using systemd- tmpfiles to manage the symlink will offer best of the 2 approach?

Cheers,

/usr/local is not our thing to manage. "Cleaning" default PATH gives you nothing except less characters in some environment variable. BP