1 |
Lemme add to the <rant/> a bit. |
2 |
|
3 |
Why does portage/emerge not use spython? I though (perhaps wrongly) that |
4 |
was one of the main reasons for a system python. If not what other |
5 |
reason is there for spython? |
6 |
|
7 |
I think it would be best to have portage use spython so those that don't |
8 |
really want a python package (I'm NOT one of them) can possibly |
9 |
(depending on other deps) get away with it. |
10 |
|
11 |
Also relying on spython instead of python would mean less problems with |
12 |
people removing python IMHO. |
13 |
|
14 |
On Tue, 2002-04-09 at 10:16, Stefan Boresch wrote: |
15 |
> |
16 |
> It seems that emerge/ portage up to 1.8.8-r1 (the last for the 1.0-rc6 |
17 |
> series) recorded md5sums in uppercase, e.g. |
18 |
> (from /var/db/pkg/sys-apps/portage-1.8.8-r1/CONTENTS) |
19 |
> |
20 |
> obj /usr/lib/portage/bin/dobin F397C62D816C80DEC70B17CB01A87B69 1013001542 |
21 |
> |
22 |
> whereas new emerge/portage-s record md5s in lower case |
23 |
> (from /var/db/pkg/sys-apps/portage-1.8.18/CONTENTS): |
24 |
> |
25 |
> obj /usr/lib/portage/bin/dobin 81b729ded424ececf0542edff43df1a3 1018330619 |
26 |
> |
27 |
> Since lately qpkg reports most files of a package as having md5 errors, |
28 |
> I assume that qpkg expects the old form (md5s in upper case). |
29 |
> |
30 |
> I can't resist the opportunity for a brief |
31 |
> |
32 |
> <rant> |
33 |
> |
34 |
> (i) Am I dreaming or is the symlink to /usr/lib/portage/bin/emerge |
35 |
> oscillating between /usr/bin and /usr/sbin depending on the portage |
36 |
> "flavor of the day. It's clear that this is not important, but |
37 |
> it can lead to annoying '/usr/(s)bin/emerge not found' messages. |
38 |
> |
39 |
> (ii) it would be fantastic if the man page for portage / emerge |
40 |
> could be kept up to date. It simply is easier to read man emerge |
41 |
> than scroll back in the output of emerge --help. Similarly, the |
42 |
> portage user guide accessible from the homepage is by now quite |
43 |
> outdated again (e.g., clean is not documented at all) Yes, one |
44 |
> can find (most of) the information, but it's not really in |
45 |
> the most visible places. |
46 |
> |
47 |
> (iii) While I agree that portage is improving dramatically and |
48 |
> rapidly, having to (re)learn some commands every day on this core |
49 |
> utility doesn't strike me as the best thing for a release ... |
50 |
> |
51 |
> Please don't get me wrong: I love gentoo, and we have deployed it |
52 |
> here on about 20 heavily used workstations since the end of last |
53 |
> year. Most screw-ups we encountered were our fault (and mostly |
54 |
> resulted from switching from 2.2.x kernels to 2.4.x etc.). I would not have |
55 |
> thought of this rant if we were talking about rc6 or some |
56 |
> hypothetical rc7. However, since upgrading |
57 |
> my experimental home machine to 1.0 I have come close to hosing |
58 |
> my system more often than 1.0-rc6 during the last 3 months. |
59 |
> (Shouldn't it be the other way around ??) |
60 |
> |
61 |
> <\rant> |
62 |
> |
63 |
> Thanks for the good work and I look forward |
64 |
> to a stabilized portage ... |
65 |
> |
66 |
> Stefan |
67 |
> |
68 |
> -- |
69 |
> Stefan Boresch |
70 |
> Institute for Theoretical Chemistry and Structural Molecular Biology |
71 |
> University of Vienna, Waehringerstr. 17 A-1090 Vienna, Austria |
72 |
> Phone: -43-1-427752715 Fax: -43-1-427752790 |
73 |
> _______________________________________________ |
74 |
> gentoo-dev mailing list |
75 |
> gentoo-dev@g.o |
76 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |