1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Wednesday 29 January 2003 16:30, Dylan Carlson wrote: |
5 |
> |
6 |
> Thanks Dan. |
7 |
> |
8 |
> In the event of a patch of one of the subpackages, you would still need to |
9 |
> recompile all of the subpackages you want again (instead of just the one |
10 |
> that has been patched). Is that a correct assumption? |
11 |
|
12 |
I see the problem. There are several ways of gettig around this. One is this: |
13 |
|
14 |
Every subpackage would have a version/revision number of its own. An ebuild |
15 |
would specify the version numbers of all the subpackages it provides. (Not in |
16 |
its filename, obviously.) When a new version's ebuild (or ebuild with a patch |
17 |
to one of the subpackages) is released, it provides a new lis of subpackage |
18 |
version numbers. If you upgrade from the old ebuild to the new one, only the |
19 |
subpackages whose version numbers changed will be emerged again, because the |
20 |
other ones are already considered merged. This situation can be simplified if |
21 |
we do not consider installed subpackages to be 'owned' (in /var/db/pkg) by a |
22 |
master package, but instead to be packages in their own right. |
23 |
|
24 |
The paradigm would be that an ebuild provieds _one or more_ packages; the |
25 |
distinction between (master) packages and subpackages would disappear. |
26 |
|
27 |
Now I must warn you these are all rough sketches and ideas off the top of my |
28 |
head, and I don't guarantee they'll actually be executed! After the freeze is |
29 |
over I'll discuss all this with the other Gentoo developersn and a decision |
30 |
will be made (by people with more say in Portage features than me, probably). |
31 |
But I'll try and convince people to do this (and possibly try to implement |
32 |
the portage features myself, I always wanted to do that...) |
33 |
|
34 |
- -- |
35 |
Dan Armak |
36 |
Gentoo Linux developer (KDE) |
37 |
Matan, Israel |
38 |
Public GPG key: http://www.gentoo.org/~danarmak/danarmak-gpg-public.key |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v1.2.1 (GNU/Linux) |
41 |
|
42 |
iD8DBQE+N+6uUI2RQ41fiVERAnkUAJ9tBs1+Mre21Asj7vSiRXOlr9W6mgCfQ95I |
43 |
7AZJylNkev7Kx5QbSyVn6VU= |
44 |
=cfck |
45 |
-----END PGP SIGNATURE----- |
46 |
|
47 |
|
48 |
-- |
49 |
gentoo-dev@g.o mailing list |