[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] [PATCH] go-module.eclass: Add GO_OPTIONAL flag
From:       Sam James <sam () gentoo ! org>
Date:       2021-11-29 4:54:09
Message-ID: E57DFE73-53E5-4121-A569-53C6652F0008 () gentoo ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


> On 28 Nov 2021, at 19:23, Zac Medico <zmedico@gentoo.org> wrote:
> 
> > [snip]
> 
> How about if we also add a GO_DEPEND variable, so that eclasshi consumers can do \
>                 something like BDEPEND="go? ( ${GO_DEPEND} )" ?
> --

My preference is to go with what we've been doing more recently (do _OPTIONAL) so \
that consumers handle things properly and we don't have to try account for various \
cases (this was the problem with eclass variables which add a USE flag or depend only
if a USE flag is set).

But that said, I can't immediately think of any such annoying edge
cases with this idea. It'd be additional to GO_OPTIONAL and it'd
ensure a sane baseline Go version is chosen. So, why not?


[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; line-break: after-white-space;" class=""><br class=""><div><br \
class=""><blockquote type="cite" class=""><div class="">On 28 Nov 2021, at 19:23, Zac \
Medico &lt;<a href="mailto:zmedico@gentoo.org" class="">zmedico@gentoo.org</a>&gt; \
wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" \
class=""><div class="content-isolator__container" style="caret-color: rgb(0, 0, 0); \
font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;"><blockquote type="cite" \
class="">[snip]</blockquote><br class="">How about if we also add a GO_DEPEND \
variable, so that eclasshi consumers can do something like BDEPEND="go? ( \
${GO_DEPEND} )" ?<br class="">--<span class="Apple-converted-space">&nbsp;</span><br \
class=""></div></div></blockquote><div><br class=""></div><div>My preference is to go \
with what we've been doing more recently (do _OPTIONAL) so that</div><div>consumers \
handle things properly and we don't have to try account for various \
cases</div><div>(this was the problem with eclass variables which add a USE flag or \
depend only</div><div>if a USE flag is set).</div><div><br class=""></div><div>But \
that said, I can't immediately think of any such annoying edge</div><div>cases with \
this idea. It'd be additional to GO_OPTIONAL and it'd</div><div>ensure a sane \
baseline Go version is chosen. So, why not?</div></div><br class=""></body></html>


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmGkXPFfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw
RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g
SDvbTwf8DFc1RbF8l4LJeK4lUfUHQA4C52GVS3Uf/7ZTcB/NjdEmZqnVVixojkik
NHUR+vkGAWnzao9MX982hdZ7be6nZsMdDRilGIZvEI9QQjCpl9ck0oym/RAJdw94
YQi17+HavKPTin+5BcVx7SyERiaBIo1/eQljInLlamT2ncXyTUrae0MSvb64TaSp
WF1BXIHw5rLevfUVbSaeMWi23b09nNywdPJIaBhI4pDLfwx2rXX2WBx/zGSmqR1/
QHpqA4qKhWG6RkaRvz/miBv8hLlG69PZmj+nPttw8A8djvU5aTj7WUudQs/zB3Ef
0iW7mjCRYZ5MbPWp0HTu1m+qEO4+mA==
=FS7r
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic