1 |
On Thu, 13 Oct 2005 13:21:21 -0500 |
2 |
Brian Harring <ferringb@g.o> wrote: |
3 |
|
4 |
> Any updates to 2.1, I'd be curious about since it's bash core is |
5 |
> the basis of 3.x |
6 |
|
7 |
The savior's bash code seems sane compared to the trunk's one. It |
8 |
doesn't have the typos ("$Header$" lines in a few .sh files and |
9 |
missing ";;" in the unpack() case for RAR), nor the bug in |
10 |
dyn_preinst() which makes portage play with the root filesystem |
11 |
(missing "local IMAGE=${D}"). A vimdiff beetween the "svn blame |
12 |
ebuild-default-functions.sh" of this two branches seems to show that |
13 |
all it mainly lacks is a bunch of cosmetic changes (commit #1893 - |
14 |
warning though: that's also were some of the above cited bugs were |
15 |
introduced, so don't apply the whole thing). |
16 |
|
17 |
Now, compared to 2.0 (and just reading changelog), i see: |
18 |
- some patches missing in both branches: some are new stuffs |
19 |
i'm sure you're already aware of (EBUILD_DEATH_HOOK, EAPI support, |
20 |
etc.), other are fixes (lchown/lchgrp for instance, but i also see |
21 |
something about .tar unpacking in changelog which seems to apply, |
22 |
etc.). |
23 |
- some missing in trunk only (CCACHE_DIR fix for instance). |
24 |
|
25 |
I'm okay to try to make some more detailed report with patches, but |
26 |
i would first like to know whether trunk is going anywhere. I mean, |
27 |
it's obvious that atm noone uses it since it's not even |
28 |
syntacticaly correct. That, plus some bugs closed as dups of #102126 |
29 |
without beeing fixed, makes me wonder... Oh, and also this recent |
30 |
email from Marius on gentoo-dev@: |
31 |
|
32 |
> On Tue, 11 Oct 2005 17:00:56 +0000 |
33 |
> Alec Joseph Warner <warnera6@×××××××.edu> wrote: |
34 |
> |
35 |
> > FYI elog is implemented in CVS ( 2.1 ). When it will be |
36 |
> > released is anyone's guess. |
37 |
> |
38 |
> 2.1? probably never, but elog will almost certainly be backported |
39 |
> to the 2.0 branch. |
40 |
> |
41 |
> Marius |
42 |
|
43 |
Anyway, don't take me wrong, i'm not trying to flame anyone about |
44 |
how portage development is done, or whatever. If the new route is |
45 |
to backport some of the long awaited features to 2.0 until 3.x is |
46 |
ready, it's fine for me. It's really just that i have a bit of |
47 |
free time this days, so i was thinking of updating a few stuffs i |
48 |
would like to see included someday (bugs #85786, #83613, #90444, |
49 |
#84884, #37498 and #34964 comes to mind), and for that i need to |
50 |
know what would be the prefered target. |
51 |
|
52 |
Thanks, |
53 |
|
54 |
-- |
55 |
TGL. |
56 |
-- |
57 |
gentoo-portage-dev@g.o mailing list |