1 |
On Donnerstag, 5. Juni 2008, Ulrich Mueller wrote: |
2 |
> >>>>> On Thu, 5 Jun 2008, Matthias Schwarzott wrote: |
3 |
> > |
4 |
> > This post is about how to create a nice upgrade path when merging two |
5 |
> > packages. |
6 |
> > The packages I care about are |
7 |
> > media-plugins/vdr-streamdev-{client,server}, that we wanted to merge into |
8 |
> > one media-plugins/vdr-streamdev package. |
9 |
> > |
10 |
> > |
11 |
> > So there seem to be different options: |
12 |
> > |
13 |
> > 1. Just create the new packages and do blocks between split and merged |
14 |
> > versions. |
15 |
> > |
16 |
> > [...] |
17 |
> > |
18 |
> > 2. Same as 1, but create dummy ebuilds vdr-streamdev-client-100 and |
19 |
> > vdr-streamdev-server-100: |
20 |
> > |
21 |
> > pkg_setup() { |
22 |
> > eerror "Please unmerge vdr-streamdev-server and emerge vdr-streamdev" |
23 |
> > die |
24 |
> > } |
25 |
> |
26 |
> With #1 the user will get a message about the blockers immediately. |
27 |
> With #2 his emerge (maybe of many packages) will needlessly die when |
28 |
> it reaches your package. |
29 |
> |
30 |
|
31 |
With #1 user will get no message, as neither the user nor the package manager |
32 |
know of the merged package that should be emerged. |
33 |
|
34 |
Maybe #2 but without call to die could be used. But that will make the plugin |
35 |
go away until user reacts on the instructions. |
36 |
|
37 |
|
38 |
> > 3. Let the dummy ebuilds RDEPEND/PDEPEND on the merged version. |
39 |
> |
40 |
> As you said yourself, #3 will result in cruft leftover on the user's |
41 |
> system. |
42 |
> |
43 |
> > #1 is the default used in the tree. |
44 |
> |
45 |
> With good reason, IMHO. This is a package manager issue which |
46 |
> shouldn't be "solved" by creating strange dummy ebuilds. |
47 |
> |
48 |
|
49 |
Matthias |
50 |
|
51 |
-- |
52 |
gentoo-dev@l.g.o mailing list |