From: NP-Hardass <NP-Hardass@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New eclass: mate
Date: Wed, 13 Apr 2016 12:21:40 -0400 [thread overview]
Message-ID: <570E7214.8040006@gentoo.org> (raw)
In-Reply-To: <20160413181920.752aa46c@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/13/2016 12:19 PM, Alexis Ballier wrote:
> On Wed, 13 Apr 2016 08:55:56 -0400 NP-Hardass
> <NP-Hardass@gentoo.org> wrote: [...]
>> The idea was partly due to consistency. Rather than calling
>> mate_this gnome2_that, it'd provide one namespace. Additionally
>> as mentioned in my initial email, since GNOME and MATE aren't
>> always in synch, if the gnome2 eclass chooses to change
>> something, and it's better that mate eclass stays with what we
>> have, all I have to do is fill in the stub, and all ebuilds
>> retain their current implementation. Otherwise, I'd have to mass
>> edit all ebuilds to replace the offending gnome2_ with mate_.
>
> yep, makes sense
>
>> Furthermore, there was a discussion a long time ago about how
>> functions shouldn't be called without an explicit inherit. That
>> means that even if the mate eclass uses gnome2, if I opt to call
>> gnome2 directly in the ebuild, I have to explicitly inherit it
>> (which mostly defeats the purpose of inheriting it in the mate
>> eclass).
>
> nah, this isnt true in your case: you can define mate.eclass' API
> to always include gnome2.eclass, making it ok to use gnome2
> functions by inheriting only mate.eclass. this means you can never
> drop gnome2.eclass from mate.eclass though, which may not be
> desired
>
I'm unfamiliar with this. Do you have a reference that I can look at?
>
>> This has an added bonus, which is that the gnome2 eclass inherits
>> gnome.org, so I have to make sure to re-inherit mate-desktop.org
>> whenever gnome2 is (re)inherited to prevent all of variables like
>> SRC_URI from being overwritten. Hope that I'm conveying that
>> logic adequately.
>
> ok, maybe you could add a comment that no ebuild should inherit
> both gnome2 & mate eclasses then
>
- --
NP-Hardass
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXDnIUAAoJEBzZQR2yrxj7WLgP/0JoEMUrbc3DjYP2SVpUM5F1
slgblQuY+2ElDpoDIoSU+GY3aSv7kv1WnH8gPRPTOYsW1XSmjXwSVbAeh0s7g8fR
779Kl3aKxHQiaNmSv4wCoBTUO3AXQrC168C13h3PebVnPVUg1df/pILbfR9vAkhR
VLL/9A3WVBLb980gywJpiEPWZC7pBIAWdD6jHdhGW9u75k4Q/Ro6jUN+NQYjexr5
S0q0CTkxJw3nJA/K+VxnLltyUoJ7i7V3MoQM4hxebTDxev6ni3rahAK7XU00Itgi
r8nAOlBbporrl2pnX/xm6HEZm14oRPo8z9Cm7Te6t7eZODtzIZlnRJkqxVVHPRWN
dhO9m8u9FpkpTsTWE2eXX9Xqwx1WLXNWxjrkiGV7urEFLI66x05pMm+JLAoyEMB1
i1ep8DuXOcTaZPQbiPOoSEcdi79pJ9kClwyRyzVCPca/Pz0n23N/OqSNVa2FTCLT
BZ5YByFO9iG90qSqCmbbjygjo51yhQJn3WqS1Kmk8N9Pdj314VQI8anWesL8Q6Ua
j9+QtIrmZ727DiLELrox/RvZ5nkr2UuO931k3iCeNSTLmhlPBSrNlQIzFL2snwp3
Y0RGgI0QUSc3l/BOP/aPhPTvPgk8JH1zjPRR5tvAPgAMoOU9JcjLDtZA2puNhp+B
UchoZyvlfnF+7rOWzcLB
=kgsm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-04-13 16:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 5:09 [gentoo-dev] [RFC] New eclass: mate NP-Hardass
2016-04-11 5:17 ` M. J. Everitt
2016-04-11 7:14 ` Daniel Campbell
2016-04-12 0:14 ` NP-Hardass
2016-04-12 2:04 ` NP-Hardass
2016-04-12 18:42 ` Pacho Ramos
2016-04-12 19:54 ` NP-Hardass
2016-04-13 9:32 ` Alexis Ballier
2016-04-13 12:55 ` NP-Hardass
2016-04-13 16:19 ` Alexis Ballier
2016-04-13 16:21 ` NP-Hardass [this message]
2016-04-14 9:07 ` Alexis Ballier
2016-04-12 18:44 ` Pacho Ramos
2016-04-12 19:44 ` NP-Hardass
2016-06-09 12:19 ` NP-Hardass
2016-06-10 3:54 ` Jason Zaman
2016-06-10 16:52 ` NP-Hardass
2016-06-15 4:18 ` Jason Zaman
2016-06-15 7:38 ` Michał Górny
2016-06-10 10:43 ` Michał Górny
2016-06-10 16:52 ` NP-Hardass
2016-06-10 17:03 ` Michał Górny
2016-06-10 13:33 ` Michał Górny
2016-06-10 16:52 ` NP-Hardass
2016-06-10 17:04 ` Michał Górny
2016-06-15 2:56 ` NP-Hardass
2016-07-01 13:45 ` Michał Górny
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=570E7214.8040006@gentoo.org \
--to=np-hardass@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