Hi,
I'm dealing with a bug in wmaker and it's becoming quite
frustrating. First some background info:
* Back in the old days of wmaker 0.6.3, it included
/usr/X11R6/bin/asclock; the afterstep package also included it.
The previous mantainer of wmaker added a diversion for that file,
Marcelo E. Magallon wrote:
> Preparing to replace wmaker 0.20.3-1 (using wmaker_0.20.3-3.deb) ...
> Removing diversion of asclock.1x to asclock.afterstep.1x...
> dpkg-divert: rename involves overwriting
> `/usr/X11R6/man/man1/asclock.1x.gz' with
>different file `/usr/X11R6/man/man1/asclock.a
Hi,
I am trying to package vdk-0.5.1 but I have some problems.
The original archive is vdk_0_5_1.tar.gz with a top directory VDK-0.5.1.
The current version of vdk is a developement version and I've decided to
call it: vdk-0.5.1-19990122 after the release day. Building the package,
I get a tar.gz
Can a Debian package mention a non-official package (available
elsewhere) in its control file?
--
I'm putting the last tweaks into a package called gri that will
go into main shortly. Last July (before I was a developer) I
asked this list about packaging different versions of it such that:
On Wed, 27 Jan 1999, Peter S Galbraith wrote:
>
> The question is as follows: Can the Debian package `gri' mention
> a non-official package `gri-2.2.0' in its control file?
Technically no. Perhaps if it were in contrib.
Could you (re-)explain why this is a good idea?
Jules
/+
Jules Bean wrote:
> On Wed, 27 Jan 1999, Peter S Galbraith wrote:
> >
> > The question is as follows: Can the Debian package `gri' mention
> > a non-official package `gri-2.2.0' in its control file?
>
> Technically no. Perhaps if it were in contrib.
How would that help disminish the size if
On Wed, Jan 27, 1999 at 09:42:11AM -0500, Peter S Galbraith wrote:
> Sure. Gri is a programming language in the same sense as
> gnuplot.
[ Out of curiosity, what exactly does gri do? ]
> But if the `replaces: gri-VERSION' line will confuse some Debian packaging
> scripts, then I will remove it
"Marcelo E. Magallon" wrote:
> On Wed, Jan 27, 1999 at 09:42:11AM -0500, Peter S Galbraith wrote:
>
> > Sure. Gri is a programming language in the same sense as
> > gnuplot.
>
> [ Out of curiosity, what exactly does gri do? ]
Description: a language for scientific graphics programming.
Gri i
Peter,
How about this approach:
Packages including the executables (and whatever else is needed) are
called gri-_ (i.e. exactly your current scheme). These
*are* uploaded to debian.
The package gri-support_ contains the other stuff, currently in
your unversioned package, *except* that it doesn'
If I have _only_ gri-VERSION_VERSION packages, then they will
never be upgraded automatically. I don't really want this.
I may simply take the dependence line out of the control file,
considering that it's not desirable to refer to a non-official
package.
Thanks,
Peter
Jules Bean wrote:
> Ho
On Wed, Jan 27, 1999 at 10:54:57AM -0500, Peter S Galbraith wrote:
> Description: a language for scientific graphics programming. [...]
/me fetches gri... nope, it's not in the distribution. Are the .deb's
available somewhere?
> gri_2.2.0 contains the a lot more stuff (HTML and postscript manual
"Marcelo E. Magallon" wrote:
> On Wed, Jan 27, 1999 at 10:54:57AM -0500, Peter S Galbraith wrote:
>
> > Description: a language for scientific graphics programming. [...]
>
> /me fetches gri... nope, it's not in the distribution. Are the .deb's
> available somewhere?
I wanted to fix this up be
On Wed, Jan 27, 1999 at 01:32:13PM -0500, Peter S Galbraith wrote:
> If I have _only_ gri-VERSION_VERSION packages, then they will
> never be upgraded automatically. I don't really want this.
>
> I may simply take the dependence line out of the control file,
> considering that it's not desirable
13 matches
Mail list logo
