Gentoo Archives: gentoo-dev

From: Patrick Lauer <patrick@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] The state and future etc. etc.
Date: Wed, 11 Jun 2014 00:50:45
Message-Id: 5397A7DB.7070502@gentoo.org
In Reply to: Re: [gentoo-dev] The state and future of the OpenRC project by Thomas Kahle
1 On 06/10/2014 03:52 AM, Thomas Kahle wrote:
2 > On 08/06/14 18:06, hasufell wrote:
3 >> I am not sure if that is a joke. You can pretty much ask most major
4 >> gentoo projects. The ones where I was involved more deeply definitely
5 >> suffer from that problem, including sunrise and games team. Science team
6 >> gave up importing major ebuilds to the tree and just let users manage
7 >> them on github, because that workflow sucks less.
8 >
9 > I disagree with that point. If you are referring to sage (or
10 > other larger science projects), then they stay in the overlay
11 > because people feel it is not worth the effort to fix the QA
12 > issues which in turn would be necessary before moving them to the
13 > main tree.
14
15 I've interacted with the nice people of the sage overlay - in that case
16 it's just the sheer amount of ebuilds, and no one on the gentoo side
17 with the time/motivation to take care of it. (I think I might have
18 borrowed a few of their ebuilds in the past)
19
20 QA issues are just an easy way to say "they be users, not us smart
21 devs", and that's just silly. If that were an issue you could start
22 fixing their ebuilds now, and once they are in good shape start
23 importing them. As no one has done that I'd say it's not a "QA" problem.
24 >
25 > From what I can tell it has nothing to do with bugzilla
26 > vs. github. For me personally bugzilla + a git tree (which is
27 > the situation we have for overlays anyway) is fine.
28
29 Ah, the old git turkey.
30
31 Personally I find github amazingly hard to figure out, usually I just
32 click around randomly in the webUI until something happens.
33
34 Migrating ebuilds is a lot of work, independent of VCS.
35
36 And if you want the git migration to happen, well, uhm, do something
37 about it. The only work that happened on it this year was me trying to
38 reproduce the last attempts to figure out where things are, a few people
39 like robbat2 providing data, and a few people like ferringb doing
40 minimal fixes to the existing migration scripts.
41
42 And I'm not even interested in using git!
43
44 Have fun,
45
46 Patrick