Subject: | |
From: | |
Reply To: | |
Date: | Tue, 30 Jul 2013 09:26:10 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, Jul 30, 2013 at 8:24 AM, Nico Kadel-Garcia <[log in to unmask]> wrote:
> On Tue, Jul 30, 2013 at 8:18 AM, Tom H <[log in to unmask]> wrote:
>> On Tue, Jul 30, 2013 at 8:05 AM, Nico Kadel-Garcia <[log in to unmask]> wrote:
>>>
>>> It is interesting. I also see Samba 3.x, not Samba 4.x. *Rats*. I was
>>> hoping for built-in Active Directory server replacements: guess I'll
>>> be rebundling the work I've done backporting Samba 4.0.7 to RHEL 6.
>>> And the slides don't say anything about the migration from SysV init
>>> scripts to systemd: that is going to be a *serious* adventure for
>>> 3rd-party open source components, like EPEL and Repoforge and atrpms.
>>
>> http://rhsummit.files.wordpress.com/2013/06/poettering_f_0945_getting_ready_for_systemd-the-new-red-hat-enterprise-linux-7-service-manager.pdf
>
> Thanks, good link. I'm just concerned it's going to cause build
> problems for *every single open source daemon* as their SRPM's or
> .spec files need to have two sets of options, one for the older SysV
> init scripts and one for systemd, or need to be split to two different
> .spec files. This is going to be so much fun!
You're welcome.
Very true. Similar to some current Fedora spec files:
%if 0%{?rhel}
...
%endif
%if 0%{?fedora}
...
%endif
An eyesore and a mess; until December 2020...
|
|
|