On Montag, 9. Juni 2008, Enrico Weigelt wrote:
* Matthias Schwarzott [EMAIL PROTECTED] schrieb:
Hi,
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
* Matthias Schwarzott [EMAIL PROTECTED] schrieb:
Well, upstream is just one file/package: vdr-streamdev-0.3.4.tgz
What I suspected.
Actually, I'm not interested in that package. Otherwise there
already would be a fork which keeps that separation.
But we want to revert this now, because
On Donnerstag, 5. Juni 2008, Rémi Cardona wrote:
Matthias Schwarzott a écrit :
With #1 user will get no message, as neither the user nor the package
manager know of the merged package that should be emerged.
I would do #1 because it's easier to do and it's the Gentoo Way (tm).
Consider
Hi there!
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
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
On Thu, Jun 5, 2008 at 4:11 PM, Ulrich Mueller [EMAIL PROTECTED] wrote:
[...]
#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.
Won't the new portage unmerge-on-blocker feature take care of
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
Matthias Schwarzott a écrit :
With #1 user will get no message, as neither the user nor the package manager
know of the merged package that should be emerged.
I would do #1 because it's easier to do and it's the Gentoo Way (tm).
Consider writing an upgrade guide and post it on Planet Gentoo
On Thu, 5 Jun 2008, Matthias Schwarzott wrote:
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
On Thu, 5 Jun 2008 13:44:06 +0200
Ulrich Mueller [EMAIL PROTECTED] wrote:
On Thu, 5 Jun 2008, Matthias Schwarzott wrote:
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.
10 matches
Mail list logo
