Olivier Crête posted on Thu, 05 Jan 2012 21:03:32 -0500 as excerpted:

> Hi,
> 
> On Thu, 2012-01-05 at 20:29 -0500, Alexandre Rostovtsev wrote:
>> Negative effects of removing the /bin/systemd symlink on 2021-05-01: an
>> unknown number of users who had forgotten to update their grub.conf
>> will discover that they can no longer boot their systems.
>> 
>> I would suggest not removing the symlink unless there is a technical
>> reason why its presence is undesirable.
> 
> Doing aggressive migrations like that should really be avoided.. But we
> know that the real long term solution is to have a /bin -> /usr/bin
> symlink.

I'm not a systemd user, but I did see his gentoo planet entry on the
topic, which explains why he's moving this fast.

http://blogs.gentoo.org/mgorny/2012/01/04/moving-systemd-into-usr-the-technical-side/

In it he said he wished he'd introduced systemd with everything on /usr in
the first place.  He sees the mistake now, and prefers to correct it while
the fewest gentoo users possible are yet using systemd.  As few are using
it at this time and that number is likely to grow over time, only making
the transition harder, he's moving much faster with the change than he'd
ordinarily move.

Keep in mind that at present, systemd has no stable keywords at all, and
only amd64 and x86 in ~arch.  For gentooers anyway systemd is thus still
beta, and he's choosing to move stuff around now while that's still the
case, instead of later, after stabilization.  Those gentooers using it now
are early adopters by definition, and should be ready to deal with this
sort of stuff.

Given that, the March and June timeframes are IMO PLENTY.  IMO, even a
mere 30 days would be reasonable for a package at this stage in the
process, and he's running a news item and giving them WAY more than that.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


Reply via email to