[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: two different packages with the same source tarball/name

On Fri, Jul 14, 2006 at 02:34:41PM +0200, Thomas Weber wrote:
> is it possible to have two different binary packages with the same
> source package name (but different upstream versions of the source)?

No.  The package with the later version will overwrite the earlier
one, and this will cause the binaries no longer built to be removed.

It is possible to have a single source package have the sources for
two versions and build two different binary packages, but in this
case you would (rightfully) get beaten with sticks.

> Reason: I'm about to package octave-forge for both Octave 2.1 and 2.9
> (you can consider octave-forge as plugin, that needs to be compiled for
> the respective version). 
>  Now, upstream provides only one tarball for *one* version; that is, the
> latest upstream tarball is meant for Octave 2.9, while previous versions
> were meant for Octave 2.1.

> I would therefore like to keep the old version for Octave 2.1 (with a
> source name of octave-forge), while packaging the latest version for
> Octave 2.9 (as well with a source name of octave-forge, but a different
> upstream version).

Just have two different source packages.  Preferably, with the same
names as the binaries they produce.

1KB		// Microsoft corollary to Hanlon's razor:
		//	Never attribute to stupidity what can be
		//	adequately explained by malice.

Reply to: