Gentoo Archives: gentoo-user

From: Enrico Weigelt <weigelt@×××××.de>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Daniel Robbins' come back ?
Date: Wed, 23 Jan 2008 17:36:55
Message-Id: 20080123173559.GC16632@nibiru.local
In Reply to: [gentoo-user] Re: Daniel Robbins' come back ? by reader@newsguy.com
1 * reader@×××××××.com <reader@×××××××.com> wrote:
2
3 > I'd hazard a guess that you may have hit a bigger problem than your
4 > comment indicates. I'm pretty sure there would be great pressure to
5 > use `quick and dirty hacks' to get stuff done when devs are nearly
6 > always overworked.
7
8 Actually, they IMHO *are*. Look at the large amount of patches in the
9 tree and the uncountable discussions which are not gentoo specific.
10 And the same happens also in other distros. An really large amount
11 of work could be done easily outside specific distros, but in an
12 more general way.
13
14 But as long as the devs refuse cooperation with such distro-agnostic
15 (meta-)projects like OSS-QM, there aren't much changes for it
16 becoming better ;-P
17
18 > > One little step out could be the OSS-QM project (http://oss-qm.metux.de/)
19 > > It collects fixes for a lot packages and makes them accessible in 100%
20 > > automated ways. So in a way it can be seen as an kind of overlay against
21 > > the upstream. Most of the patches are things that upstream's tend to forget
22 > > but importand for fully automated builds (eg. proper relocation, clean
23 > > feature switching, fixing buildfiles, pkg-config, etc) - they do NOT harm
24 > > the core functionality. So exactly what the vast majority of distro's
25 > > patches do, but in generic (distro agnostic) ways.
26 >
27 > The theory sounds very sensible.
28 > After looking at that page and some of the links briefly it wasn't
29 > clear to me where this is being used. I see a very short list of pkgs
30 > being worked on.. and guessing it is because of being short handed
31 > there.
32
33 There's not documentation yet. Feel free to join the maillist/board and
34 improve it ;-)
35
36 > But what wasn't clear is how work comes in and where it goes when it
37 > goes out.
38
39 Well, everyone is free to join the project as an "vendor".
40 (vendor = someone who supplies code). Each vendor has it's own namespace,
41 for patches as well as patchsets (patchset = list of patches for an specific
42 version of an specific package). You can see the bunch of patchsets from
43 some vendor as an kind of overlay against the upstream. Combined with CSDB
44 you can fetch source + patchset for an specific package in an specific
45 version completely automatically.
46
47 > PS-The `help' link under `navigation' brings up what appears to be
48 > something it is not intended to, and may even be a hack on those pages
49 > or something. (The content that comes up may even be sort of off the
50 > wall.)
51
52 The usual wiki vandalism :(
53
54
55 cu
56 --
57 ---------------------------------------------------------------------
58 Enrico Weigelt == metux IT service - http://www.metux.de/
59 ---------------------------------------------------------------------
60 Please visit the OpenSource QM Taskforce:
61 http://wiki.metux.de/public/OpenSource_QM_Taskforce
62 Patches / Fixes for a lot dozens of packages in dozens of versions:
63 http://patches.metux.de/
64 ---------------------------------------------------------------------
65 --
66 gentoo-user@l.g.o mailing list

Replies