1 |
On Wed, 2003-06-04 at 20:52, Joseph Carter wrote: |
2 |
> Any plans to cooperate with the fink people on this? That might be |
3 |
> getting a bit out of the realm of what's normal and expected for Gentoo, |
4 |
> but I happen to think that portage is a lot better suited to building fink |
5 |
> packages than anything Debian's got these days. |
6 |
ah, i cannot resist responding to that jab from a developer's |
7 |
perspective: |
8 |
|
9 |
advantages of DebianStyle(R)(TM)(C): |
10 |
- extensive set of tools to validate and QA packages (lintian is really |
11 |
full-featured) |
12 |
- picky policy on where things should go, what should always be in a |
13 |
package, etc. and its documented, whereas some things are still kind of |
14 |
up in the air for Gentoo, or more just guidelines...gives a consistent |
15 |
feel to Debian. |
16 |
|
17 |
disadvantages of DebianStyle(R)(TM)(C): |
18 |
- takes too long to get your head around the complete building process, |
19 |
there are lots of docs and policy to take in, in more than one set of |
20 |
documentation |
21 |
- too many ways to set up the build process...the policy just dictates |
22 |
some expected files and expected debian/rules targets, so you're free to |
23 |
do it in your own way, which leads to wheel reinvention. |
24 |
- ad-hoc external patch (changes outside of Debian-specific diffs) |
25 |
mechanisms (dpatch, dbs, hand-rolled). dpatch requires you to create a |
26 |
damn script for each external patch you want to apply (argh!!). there is |
27 |
a tool to help with this, but still... |
28 |
- too much legacy stuff hanging around (probably understandable, given |
29 |
~8000 packages), so improvements to the package build system as a whole |
30 |
are in tiny tiny increments: they're too scared of breaking backwards |
31 |
compatibility for new features. NB: how is Gentoo going to handle |
32 |
scaling while maintaining Portage feature increase? |
33 |
- sucky kernel module building system (tried building nvidia-kernel on |
34 |
Debian? heh...due to it using make-kpkg, less than intuitive compared to |
35 |
'emerge nvidia-kernel') |
36 |
|
37 |
disadvantages of ebuilds i've noticed: |
38 |
- one ebuild can't generate multiple installed packages. this is why i |
39 |
suppose eclasses were invented. |
40 |
|
41 |
by no means a definitive list, but for those of you that aren't from a |
42 |
Debian maintainer background, some things i ran into during my tenure. |
43 |
|
44 |
Gentoo isn't doing all that badly, though. Debian was pretty ad-hoc in |
45 |
the early days, so i'm positive for Gentoo's future. |
46 |
|
47 |
i still use both Debian and Gentoo :) |
48 |
|
49 |
leon |
50 |
|
51 |
|
52 |
-- |
53 |
gentoo-dev@g.o mailing list |