Lennart Poettering writes:
> But then we'd introduce two macros now, for two old distros, that make
> no sense on the next distros anymore but we could never get rid of them
> anymore, because we'd break the old packages...
So what? It's not like the carrying cost of redundant macros is
anything
On Thu, 13.09.12 07:47, Bruno Wolff III (br...@wolff.to) wrote:
> >Of course we could introduce new macros for both A and B, so that we'd
> >have three macros, covering all three operations. But who'd be helped
> >with that? We should introduce new stuff only for new distros, and maybe
> >backport
On Thu, Sep 13, 2012 at 09:10:45 +0200,
Lennart Poettering wrote:
In other words:
A) There's one postinst script that invokes "systemctl enable"
B) There's another one that does not invoke systemctl, and leaves the service
off
C) There's a third one that invokes "systemctl preset"
In F16/F1
On 13 September 2012 09:10, Lennart Poettering wrote:
> On Thu, 13.09.12 08:48, Simone Caronni (negativ...@gmail.com) wrote:
> Hope this clarifies this a bit.
Thanks for the explanation!
Regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose
sight of the shore
On Thu, 13.09.12 08:48, Simone Caronni (negativ...@gmail.com) wrote:
> Hello,
>
> On 13 September 2012 08:06, Lennart Poettering wrote:
> > Since F16/F17 do not have presets we cannot just port those macros
> > there. What is one macro in F18 would map to two macros in F16/F17.
>
> Can you plea
Hello,
On 13 September 2012 08:06, Lennart Poettering wrote:
> Since F16/F17 do not have presets we cannot just port those macros
> there. What is one macro in F18 would map to two macros in F16/F17.
Can you please point me to the two macros? I only see a small difference.
I applied the macros
On Fri, 31.08.12 09:21, Simone Caronni (negativ...@gmail.com) wrote:
> 2- What's the status of the back-port of those macros to F16/F17 (with a
> different expansion of course)? Is it under evaluation? Should I wait for
> the resolution of this before starting to add the macros?
Since F16/F17 do
On 31 August 2012 15:25, Tom Callaway wrote:
> > 1- Since the packages I mantain build on RHEL5+ and Fedora 16+ (and have
> > for a long time), can I assume these macros in the spec file is optional?
> > If that's the case, what should I do with the bugs opened?
>
> I'd have to defer to FESCo on
On 08/31/2012 03:21 AM, Simone Caronni wrote:
> According to the systemd snippets [1], the new macros should be only for
> NEW packages, i.e. those that never had a SysV init script.
The macros apply for both NEW packages and converted packages, in F18+.
There are additional triggers needed if con
