1 |
I totally agree with this (though I am not yet a dev). From the |
2 |
installation perspective (I'm the GLIS guy), it makes a very small |
3 |
stage 1 tarball, which is great for net installations. It also removes |
4 |
interpreter upgrade problems. For instance, python 2.3 is already in |
5 |
most other distros as a stable package. Bindings for other languages |
6 |
also become really easy. C/C++, while not glamorous, is a workhorse. |
7 |
Hope I'm not being too much of a "freak". Whatever language it gets |
8 |
done in, I support it fully. |
9 |
|
10 |
my $0.02 |
11 |
|
12 |
Nathaniel |
13 |
On Dec 5, 2003, at 10:47 AM, Luke-Jr wrote: |
14 |
|
15 |
> -----BEGIN PGP SIGNED MESSAGE----- |
16 |
> Hash: SHA1 |
17 |
> |
18 |
> On Friday 05 December 2003 09:58 am, George Shapovalov wrote: |
19 |
>> On the other hand I understand the desire to stay clear off the C/C++ |
20 |
>> use |
21 |
>> and completely support it. |
22 |
> Personally, I see C/C++ as an option that really should be considered |
23 |
> not for |
24 |
> being widely known, easy or readable, but because it would allow |
25 |
> Portage to |
26 |
> depend on *only* glibc, which could mean that there would only be 2 |
27 |
> critical |
28 |
> packages that could break it and even then, staticly linking Portage |
29 |
> could |
30 |
> remove the glibc dependency (I think). |
31 |
> Might it be a good idea to maintain a minimal Portage in C for recovery |
32 |
> purposes even if portage-ng decides to go with another language? |
33 |
> - -- |
34 |
> Luke-Jr |
35 |
> Developer, Gentoo Linux |
36 |
> http://www.gentoo.org/ |
37 |
> -----BEGIN PGP SIGNATURE----- |
38 |
> Version: GnuPG v1.2.3 (GNU/Linux) |
39 |
> |
40 |
> iD8DBQE/0KiwZl/BHdU+lYMRAlf3AJ9xRwqgjEg6pxanwVqLa/sdMMvWsACgjd4D |
41 |
> 6uqESnoda5xazl2fNY3gvog= |
42 |
> =Tk4Q |
43 |
> -----END PGP SIGNATURE----- |
44 |
> |
45 |
> -- |
46 |
> gentoo-dev@g.o mailing list |
47 |
> |
48 |
|
49 |
|
50 |
-- |
51 |
gentoo-dev@g.o mailing list |