From: Michael Orlitzky <mjo@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PR] ivy, mvn, sbt, gradle builders improvement for ebuild development
Date: Mon, 20 Apr 2020 15:23:15 -0400 [thread overview]
Message-ID: <e78151e8-3c3c-1474-7df5-4ffd5fed65b0@gentoo.org> (raw)
In-Reply-To: <20200420115851.046ca63d@moya.linuxfreak.ca>
On 4/20/20 2:58 PM, Patrick McLean wrote:
>>
>> You keep saying that, but the fact that dev-go/* is filled with trash
>> that has your name on it prevents anyone else from doing a better job.
>>
> Ad-hominen attacks are unwarranted, please refrain from them. I challenge you to find *anything* in dev-go/* with my name on it.
You quoted me one sentence prior saying that it's the Go ebuilds that
are trash and not anyone personally. But OK, I should have said "Sony
Interactive Entertainment" there instead of "you."
> Are you volunteering to do the work to package go packages? The people doing the work generally get to decide how that work gets done, and which approach they would like to take. The upstream situation makes it very labour-intensive to do the work in a the way you are proposing (many packages would end up with hundreds to thousands of packages in the tree). Separating everything out in to separate packages will just increase the maintenance load exponentially, with no gains as go upstreams version lock all their dependencies.
>
I'm volunteering to work on one or two small Go packages. Can I convert
the eclass to use dynamic linking? Can I start replacing your packages
with my own if I need them as dependencies? I suspect not, and that's
one of many reasons why "having things in ::gentoo does not affect
anyone who does not use them" is bullshit.
next prev parent reply other threads:[~2020-04-20 19:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 15:23 [gentoo-dev] [gentoo-java][PR] ivy, mvn, sbt, gradle builders improvement for ebuild development Samuel Bernardo
2020-04-11 1:06 ` Benda Xu
2020-04-18 16:07 ` Samuel Bernardo
2020-04-19 4:31 ` [gentoo-dev] Re: [PR] " Benda Xu
2020-04-19 14:55 ` Samuel Bernardo
2020-04-19 15:37 ` Michael Orlitzky
2020-04-19 16:14 ` Alec Warner
2020-04-19 19:41 ` Samuel Bernardo
2020-04-19 20:09 ` Michael Orlitzky
2020-04-19 21:37 ` Samuel Bernardo
2020-04-20 20:21 ` Georg Rudoy
2020-04-20 20:51 ` Michael Orlitzky
2020-04-20 21:05 ` Georg Rudoy
2020-04-20 21:38 ` Michael Orlitzky
2020-04-20 21:48 ` Georg Rudoy
2020-04-21 0:12 ` Michael Orlitzky
2020-04-20 17:31 ` Patrick McLean
2020-04-20 18:07 ` Michael Orlitzky
2020-04-20 18:58 ` Patrick McLean
2020-04-20 19:23 ` Michael Orlitzky [this message]
2020-04-20 20:19 ` Patrick McLean
2020-04-20 21:03 ` Michael Orlitzky
2020-04-20 21:25 ` Patrick McLean
2020-04-20 22:08 ` Michael Orlitzky
2020-04-20 21:04 ` William Hubbs
2020-04-21 5:50 ` Michał Górny
2020-04-21 11:08 ` Samuel Bernardo
2020-04-21 15:31 ` William Hubbs
2020-04-20 19:27 ` Rich Freeman
2020-04-20 20:55 ` Samuel Bernardo
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=e78151e8-3c3c-1474-7df5-4ffd5fed65b0@gentoo.org \
--to=mjo@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