From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny
Date: Fri, 23 Mar 2018 11:53:40 +0100 [thread overview]
Message-ID: <23220.56500.47110.798699@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <0559e21f-edcb-986f-0a0b-1bc54bc169a6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
>>>>> On Fri, 23 Mar 2018, Francesco Riosa wrote:
> Il 23/03/2018 10:48, Ulrich Mueller ha scritto:
>> Conceptually that makes no sense. sys-devel/gcc is the name of an
>> upstream package, so what does it even mean to mask it in one
>> repository but not in another? If it's the same package, then it
>> should behave in the same way, regardless of the repository its
>> ebuild it hosted in (or the package being installed, in which case
>> it is no longer in an ebuild repository).
>> If it is a different package however, then it should have a
>> different name.
> Sorry to say it bluntly but this make no sense at all, even changing
> a USE flag make the package behave wildly differently.
Right, So you want USE dependencies, which we have. Nothing stops a
package in an overlay from having additional USE flags.
> Once we agree that an upstream (complex enough) package may have
> different incarnations two ebuilds from different maintainers may
> please differently the user.
Still, masking is the wrong way to express such preferences. If you
package.mask sys-devel/gcc then you say that something is wrong with
that package. Which I believe is not what you want to express here.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-03-23 10:53 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
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 [this message]
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=23220.56500.47110.798699@a1i15.kph.uni-mainz.de \
--to=ulm@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