From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny
Date: Thu, 22 Mar 2018 21:27:00 +0100 [thread overview]
Message-ID: <1521750420.836.28.camel@gentoo.org> (raw)
In-Reply-To: <20180322201715.05be1df8@symphony.aura-online.co.uk>
W dniu czw, 22.03.2018 o godzinie 20∶17 +0000, użytkownik James Le
Cuirot napisał:
> On Thu, 22 Mar 2018 20:03:46 +0100
> Michał Górny <mgorny@gentoo.org> wrote:
>
> > After 2+ years of repeating disagreements with Portage maintainer(s)
> > I have finally decided to fork Portage. My little fork uses technical
> > name of 'portage[mgorny]' [1] (to distinguish it from mainline Portage),
> > and aims to focus on cleaning up code and adding useful features with
> > less concern for infinite bug-by-bug compatibility.
>
> I hope you will continue with our efforts to drive regular Portage
> forwards too. It's been a long road but also very productive.
>
> I notice that your fork cannot be installed at the same time as regular
> Portage. I think this will really hinder any interest in it.
Making them co-installable would require creating divergent packages
and eventually making a huge mess of almost-identical-but-different
Python modules. It's not worth the effort, especially that the two
projects are not that divergent.
> As
> Gentoo developers, we obviously have to make sure things work with the
> official package manager and that goes for you too. Would it be
> possible for them to coexist? I'm not saying I'll try it though, just
> making a suggestion. :)
As Gentoo developers, we have have to make sure things work with *all*
package managers. That's why we have standards and policies. Unlike
mainline Portage, portage[mgorny] follows those policies strictly
and therefore any ebuild that works with it should also work with
mainline Portage.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2018-03-22 20:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 19:03 [gentoo-dev] New Portage fork: sys-apps/portage-mgorny Michał Górny
2018-03-22 20:17 ` James Le Cuirot
2018-03-22 20:27 ` Michał Górny [this message]
2018-03-22 20:31 ` Zac Medico
2018-03-23 1:01 ` Herb Miller Jr.
2018-03-23 8:28 ` Michał Górny
2018-03-22 21:47 ` Consus
2018-03-22 22:06 ` Michał Górny
2018-03-22 22:52 ` Geaaru
2018-03-22 23:22 ` Zac Medico
2018-03-23 8:31 ` Michał Górny
2018-03-23 9:48 ` Ulrich Mueller
2018-03-23 10:18 ` Francesco Riosa
2018-03-23 10:38 ` Franz Fellner
2018-03-23 10:53 ` Ulrich Mueller
2018-03-24 7:02 ` Kent Fredric
2018-03-24 8:02 ` Michał Górny
2018-03-24 9:01 ` Kent Fredric
2018-03-24 12:54 ` Rich Freeman
2018-03-24 18:27 ` Zac Medico
2018-03-24 20:33 ` Kent Fredric
2018-03-24 20:44 ` Zac Medico
2018-03-25 2:26 ` Kent Fredric
2018-03-25 4:43 ` Zac Medico
2018-03-25 9:02 ` Kent Fredric
2018-03-26 7:48 ` Zac Medico
2018-03-23 10:38 ` Roy Bamford
2018-03-23 10:59 ` Ulrich Mueller
2018-03-23 13:27 ` Rich Freeman
2018-03-23 14:25 ` Arve Barsnes
2018-03-23 16:20 ` Geaaru
2018-03-23 16:23 ` Patrick Steinhardt
2018-03-23 20:16 ` Georgy Yakovlev
2018-03-23 17:44 ` Patrick McLean
2018-03-26 16:48 ` Thomas Deutschmann
2018-03-26 18:36 ` Zac Medico
2018-03-25 10:13 ` Vadim A. Misbakh-Soloviov
2018-03-28 4:42 ` [gentoo-dev] " Duncan
2018-03-23 11:25 ` [gentoo-dev] " Consus
2018-05-19 15:53 ` Consus
2018-05-22 20:35 ` Michał Górny
2018-05-28 2:45 ` Richard Yao
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=1521750420.836.28.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@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