From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Debian forked, because of systemd brouhaha
Date: Mon, 1 Dec 2014 15:22:49 +0700 [thread overview]
Message-ID: <CAA2qdGWgyEWx=3FeeWRS2a72i-tRTA+H03D_iLjKcqnQ2ELyDg@mail.gmail.com> (raw)
In-Reply-To: <20141130205450.0c00f47e@sepulchrave.remarqs>
On Mon, Dec 1, 2014 at 9:54 AM, »Q« <boxcars@gmx.net> wrote:
> On Sun, 30 Nov 2014 07:43:21 +0300
> Andrew Savchenko <bircoph@gentoo.org> wrote:
>
>> On Sat, 29 Nov 2014 17:32:08 +0100 Marc Stürmer wrote:
>> > Am 29.11.2014 um 11:11 schrieb Pandu Poluan:
>> >
>> > > What do you think, people? Shouldn't we offer them our eudev
>> > > project to assist?
>> >
>> > Since Eudev has always been opensource under the GPLv2, like udev
>> > too, there's no need to /offer/ it.
>> >
>> > If they choose to use it, they can use it, no offer/questions
>> > necessary. Simple.
>>
>> As far as I understand, Pandu meant "we can recommend them to use",
>> but not some offer in commercial or proprietary terms.
Yup, that's what I meant.
Sorry for the confusion; I'm not a native English speaker, so I may
have used an improper verb there :-)
> They've added something called "devuan-eudev" to their github workspace
> today, <https://github.com/devuan/devuan-eudev>. It would be nice if
> there could be one eudev project with the aim of supporting Gentoo,
> Devuan, and whatever other distros want to use it. Or if there must be
> multiple eudevs, it would be nice if the different teams could
> communicate and maybe take some patches from each other. (I'm no dev,
> so take my opinions on "what would be nice" for development with a
> chunk of salt.)
>
Actually, that's my point by saying "offer": Rather than letting them
build eudev from scratch, let's work together on the eudev we have,
promote it to something distro-neutral, then let Gentoo and Devuan
(and whatever other distros) derive from that 'upstream'
Uh, I do make myself clear(er) here, don't I?
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pandu.poluan.info/blog/
• Linked-In : http://id.linkedin.com/in/pepoluan
next prev parent reply other threads:[~2014-12-01 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 10:11 [gentoo-user] Debian forked, because of systemd brouhaha Pandu Poluan
2014-11-29 11:02 ` Neil Bothwick
2014-11-29 12:15 ` the
2014-11-29 16:32 ` Marc Stürmer
2014-11-30 4:43 ` Andrew Savchenko
2014-12-01 2:54 ` [gentoo-user] " »Q«
2014-12-01 8:22 ` Pandu Poluan [this message]
2014-12-01 8:36 ` Marc Stürmer
2014-11-29 23:30 ` [gentoo-user] " Marc Stuermer
2014-11-29 23:45 ` Rich Freeman
2014-11-30 2:01 ` Bill Kenworthy
2014-11-30 3:32 ` Rich Freeman
2014-11-30 4:35 ` Andrew Savchenko
2014-11-30 12:10 ` Bill Kenworthy
2014-11-30 10:07 ` Marc Stürmer
2014-11-30 11:44 ` Philip Webb
2014-11-30 12:29 ` Marc Stürmer
2014-11-30 13:01 ` Mick
2014-11-30 13:13 ` Neil Bothwick
2014-11-30 16:33 ` Mick
2014-11-30 19:40 ` Neil Bothwick
2014-11-30 16:39 ` Daniel Frey
2014-11-30 17:14 ` Marc Stürmer
2014-12-01 11:54 ` Joerg Schilling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2qdGWgyEWx=3FeeWRS2a72i-tRTA+H03D_iLjKcqnQ2ELyDg@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox