On Fri, Jan 25, 2013 at 4:25 PM, Marcela Mašláňová <mmaslano(a)redhat.com> wrote:
On 01/25/2013 12:17 AM, Adam Williamson wrote:
>
> On Thu, 2013-01-24 at 23:03 +0000, "Jóhann B. Guðmundsson" wrote:
>
>> It's best to rip the bandage of this in one release.
>>
>> The churn from this should have been more or less covered when we
>> implement biosdevname so the fallout from this change should be minimal
>> if any...
>
>
> I see the 's' word in there ;)
>
> That's always the hope, and then we meet the cold reality, where someone
> just patched 'em1' into everything and hoped that was good enough. But
> sure, 'damn the torpedoes' is a viable approach too. I guess I was just
> kind of hoping F19 would be a release without yet more churn in the core
> system where we could try and stabilize things a bit.
>
I agree. The scope says no impact, but who knows how many packages depend on
hardcoded names.
It's not only "em1" mistakenly hard-coded in applications; it's
user's
saved configuration, scripts etc., where often there is no practical
alternative to "hard-coding".
Mirek