On 2018-07-26 11:09 PM, spiralofhope wrote:
On Thu, 26 Jul 2018 21:49:45 +0900
Olaf Meeuwissen wrote:
KatolaZ writes:
The medium-term plan is to replace libsystemd0 with a libnosystemd
...
+1, although I'd prefer a more original and playful name ;-)
libsystemc =p
That's going to fly b
On 07/27/2018 10:55 AM, goli...@dyne.org wrote:
On 2018-07-27 09:37, Olaf Meeuwissen wrote:
I did not mean to drop the hack. I only meant to not make it part of a
package with a name that associates with init-freedom. Keep the hack
and put it in a differently named package. Maybe something
On Fri, 27 Jul 2018 10:55:21 -0500, goli...@dyne.org wrote in message
<8bf10b143787869cbb7e72c798927...@dyne.org>:
> On 2018-07-27 09:37, Olaf Meeuwissen wrote:
> >
> > I did not mean to drop the hack. I only meant to not make it part
> > of a package with a name that associates with init-freed
On Thu, 26 Jul 2018 22:00:06 +0900
Olaf Meeuwissen wrote:
> I just realized that true init-freedom should be systemd-inclusive, so
> don't put that dpkg-cfg hack in any kind of "init-freedom" package,
> please.
I'm pretty sure I was the person who originated the phrase
"init-freedom". This can
On 2018-07-27 09:37, Olaf Meeuwissen wrote:
I did not mean to drop the hack. I only meant to not make it part of a
package with a name that associates with init-freedom. Keep the hack
and put it in a differently named package. Maybe something like
rabid-foaming-at-the-mouth-systemd-referen
Hi,
Arnt Karlsen writes:
> On Thu, 26 Jul 2018 22:00:06 +0900, Olaf wrote in message
> <87va92gnjd@member.fsf.org>:
>
>> Hi,
>>
>> Minor correction in-lined below.
>>
>> Olaf Meeuwissen writes:
>>
>> > Hi,
>> >
>> > KatolaZ writes:
>> >
>> >> The medium-term plan is to replace libsystemd0 wit
On Thu, 26 Jul 2018 22:00:06 +0900, Olaf wrote in message
<87va92gnjd@member.fsf.org>:
> Hi,
>
> Minor correction in-lined below.
>
> Olaf Meeuwissen writes:
>
> > Hi,
> >
> > KatolaZ writes:
> >
> >> The medium-term plan is to replace libsystemd0 with a libnosystemd
> >> which Provides:
On Thu, Jul 26, 2018 at 07:09:59PM +, Daniel Abrecht wrote:
[cut]
>
> Another problem could arise though, how stable are the systemd APIs? I
> once wrote https://git.devuan.org/devuan-packages/sd_journal_shim , it
> generates the libjournal library and just provides a subset of
> systemds lo
On Thu, 26 Jul 2018 21:49:45 +0900
Olaf Meeuwissen wrote:
> KatolaZ writes:
>
> > The medium-term plan is to replace libsystemd0 with a libnosystemd
> > ...
>
> +1, although I'd prefer a more original and playful name ;-)
libsystemc =p
___
Dng mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2018-07-26 14:32, info at smallinnovations dot nl wrote:
> It would help maintaining packages that depend on systemd too. You
> only would have to add some code to use the libnosystemd instead
> of libsystemd0.
If a libnosystemd package provides
On 26-07-18 18:21, Steve Litt wrote:
> On Thu, 26 Jul 2018 16:13:41 +0200
> info at smallinnovations dot nl wrote:
>
>> No it would not, it will offer developers who want to use some systemd
>> API call in their development the opportunity to do so for nosystemd
>> systems too.
> Eu!
>
On Thu, 26 Jul 2018 16:13:41 +0200
info at smallinnovations dot nl wrote:
> No it would not, it will offer developers who want to use some systemd
> API call in their development the opportunity to do so for nosystemd
> systems too.
Eu!
What makes you different from the devs at Gnom
On 26-07-18 16:22, KatolaZ wrote:
> On Thu, Jul 26, 2018 at 04:13:41PM +0200, info at smallinnovations dot nl
> wrote:
>
> [cut]
>
> I guess our main problem is to maintain packages that depend on
> systemd, and provide alternatives for that dependency. Not to ease the
> life of developers that de
On Thu, Jul 26, 2018 at 04:13:41PM +0200, info at smallinnovations dot nl wrote:
[cut]
> > But that would entail forking and patching all the packages which use
> > libsystemd to force them to check if systemd is available... which is
> > exactly what we are trying to avoid by nooping libsystemd0
On 26-07-18 14:05, KatolaZ wrote:
>> Of course does the libsystemd API not provide it, but we can. First call
>> to libsystemd API == systemd installed? If no, call to libnosystemd API
>> which init system == installed? Or something like that. But put in place
>> a mechanism that allows to shell ou
Hi,
Minor correction in-lined below.
Olaf Meeuwissen writes:
> Hi,
>
> KatolaZ writes:
>
>> The medium-term plan is to replace libsystemd0 with a libnosystemd
>> which Provides: libsystemd0 and noops everything, with the possibility
>> of shelling-out some actions, if the admin wants so. We will
Hi,
KatolaZ writes:
> The medium-term plan is to replace libsystemd0 with a libnosystemd
> which Provides: libsystemd0 and noops everything, with the possibility
> of shelling-out some actions, if the admin wants so. We will get
> there.
+1, although I'd prefer a more original and playful name ;
17 matches
Mail list logo
