On Donnerstag, 5. Juni 2008, Ulrich Mueller wrote:
> >>>>> On Thu, 5 Jun 2008, Matthias Schwarzott wrote:
> >
> > This post is about how to create a nice upgrade path when merging two
> > packages.
> > The packages I care about are
> > media-plugins/vdr-streamdev-{client,server}, that we wanted to merge into
> > one media-plugins/vdr-streamdev package.
> >
> >
> > So there seem to be different options:
> >
> > 1. Just create the new packages and do blocks between split and merged
> > versions.
> >
> > [...]
> >
> > 2. Same as 1, but create dummy ebuilds vdr-streamdev-client-100 and
> > vdr-streamdev-server-100:
> >
> > pkg_setup() {
> > eerror "Please unmerge vdr-streamdev-server and emerge vdr-streamdev"
> > die
> > }
>
> With #1 the user will get a message about the blockers immediately.
> With #2 his emerge (maybe of many packages) will needlessly die when
> it reaches your package.
>
With #1 user will get no message, as neither the user nor the package manager
know of the merged package that should be emerged.
Maybe #2 but without call to die could be used. But that will make the plugin
go away until user reacts on the instructions.
> > 3. Let the dummy ebuilds RDEPEND/PDEPEND on the merged version.
>
> As you said yourself, #3 will result in cruft leftover on the user's
> system.
>
> > #1 is the default used in the tree.
>
> With good reason, IMHO. This is a package manager issue which
> shouldn't be "solved" by creating strange dummy ebuilds.
>
Matthias
--
gentoo-dev@lists.gentoo.org mailing list
