1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Saturday 04 October 2003 02:15 pm, Stuart Herbert wrote: |
5 |
> On Saturday 04 October 2003 3:04 pm, Luke-Jr wrote: |
6 |
> > emerge linux-mm-src, then. or emerge linux-redhat-src, if you prefer. |
7 |
> |
8 |
> Sorry, but renaming packages always makes a mess of upgrades. I've done it |
9 |
> myself in the past, but I'm reluctant to do it again until Portage provides |
10 |
> us with tools to automate the migration for users. |
11 |
I thought Portage did automate renaming of packages? Isn't that what those |
12 |
Q#-YYYY are for? |
13 |
> |
14 |
> Besides, what value is there in adding 'linux-' in front of the different |
15 |
> kernel names? I know Gentoo's being ported to run on more than just the |
16 |
> Linux kernel, but still. Seems like change for change's sake. |
17 |
Packages don't neccesarilly need to be a kernel at all. If -src were |
18 |
implemented, there would be apache-src, kdelibs-src, gcc-src, etc... |
19 |
> |
20 |
> > Just because you choose not to use it doesn't mean you should be forcing |
21 |
> > other people not to be able to. This provides the *option* to use it. |
22 |
> > Options are always best. |
23 |
> |
24 |
> Simplicity is always best. Options are good, but only when they add |
25 |
> measurable value. Or when they're just too cool to leave out ;-) |
26 |
As it is, kernels are a non-standard set of ebuilds. There is always value is |
27 |
standardizing things. |
28 |
> |
29 |
> > That annoying habit is what should be fixed, then. Using a bug as a |
30 |
> > reason to not implement a feature isn't a good idea... =p |
31 |
> |
32 |
> If it was that easy, I think someone would have fixed it by now ... ;-) |
33 |
> Tbh, the fix is probably just to slot the module, using a combination of |
34 |
> the target kernel version and the module's version. |
35 |
w/o the module's version. You don't want to install ALSA 0.9.2 and 0.9.3 at |
36 |
the same time, do you? |
37 |
> |
38 |
> If what you're proposing are changes *just* to genkernel, then I don't |
39 |
> really care what you do. But you're talking like you're suggesting |
40 |
> fundamental changes to the kernel ebuilds themselves. *That's* what I'm |
41 |
> objecting to ;-) |
42 |
It would be making the linux ebuilds' src_compile actually do what it was |
43 |
meant to do. It would also be adding a feature to portage so one could append |
44 |
- -src to the end of any ebuild and get only the result of src_unpack in |
45 |
their /usr/src dir. |
46 |
|
47 |
> |
48 |
> > For the most part, what I am suggesting is adding options, not removing |
49 |
> > them. Where people used vanilla-sources in the past (which is quite vague |
50 |
> > actually; why should one assume -sources means it's Linux?), |
51 |
> |
52 |
> Erm, because the package is actually called sys-kernel/vanilla-sources, |
53 |
> perhaps? ;-) And because the distribution is known as Gentoo Linux? ;-) |
54 |
IMO, categories are merely useful for when searching for packages and |
55 |
shouldn't really be needed for knowing what a package is especially since two |
56 |
packages cannot have the same name. If pkg name conflicts never happened, I'd |
57 |
suggest using only the package names where category/package is often used. |
58 |
I refer to Gentoo as only Gentoo. When referring to my OS, I call it Gentoo |
59 |
GNU/Linux. I also make reference to Gentoo BSD, Gentoo OS X, or Gentoo GNU |
60 |
(HURD==completely GNU) occasionally. |
61 |
Once Gentoo BSD or Gentoo OS X get to a usable stage, I'd assume the website |
62 |
would be updated to reflect that Gentoo is more than just Linux or perhaps |
63 |
seperate Gentoo BSD/OSX/etc websites would be setup. |
64 |
> |
65 |
> Seriously, I do see the problem you're describing. But before you go |
66 |
> around renaming packages, please implement a solution in Portage that will |
67 |
> automatically handle 'emerge -u' when the package has been renamed. |
68 |
AFAIK, this already should work. Note I don't use -u nor the world metakeyword |
69 |
(at least until Portage supports sticky USE), though. |
70 |
- -- |
71 |
Luke-Jr |
72 |
Developer, Gentoo Linux |
73 |
http://www.gentoo.org/ |
74 |
-----BEGIN PGP SIGNATURE----- |
75 |
Version: GnuPG v1.2.3 (GNU/Linux) |
76 |
|
77 |
iD8DBQE/ftr2Zl/BHdU+lYMRAkY6AJ9DncM6yOfqWDCuPB3U9by4Reg4nwCfX2GI |
78 |
sVbRtUR2xiujxlj/WdRPpI8= |
79 |
=v4Os |
80 |
-----END PGP SIGNATURE----- |
81 |
|
82 |
|
83 |
-- |
84 |
gentoo-dev@g.o mailing list |