Example files now have http access

Hi, Thanks to a suggestion by aph, the example debian files I have been giving out are now available at and the full tar file at enjoy. manoj -- It was pity stayed his hand. "Pity

Re: One source, two binary packages

On 9 Apr 1998, Ben Gertzfield wrote: > > "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: > > Santiago> I disagree here. > > Santiago> If you put this in a different debian/rules target > Santiago> (called, for example, automake-refresh), then you and > Santiago> only

Re: One source, two binary packages

-BEGIN PGP SIGNED MESSAGE- On 9 Apr 1998, Ben Gertzfield wrote: > For the GIMP packages, it is required; they ship with a libtool > that is incompatible with Debian policy. I have to run > automake/aclocal/autoconf every single time the package builds > to remove all vestiges of the old l

Re: One source, two binary packages

> "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: Santiago> I disagree here. Santiago> If you put this in a different debian/rules target Santiago> (called, for example, automake-refresh), then you and Santiago> only you would be forced to have automake and autoconf

Re: ssh-agent (continuing saga)

At 11:57 -0500 1998-04-09, Zed Pobre wrote: >Okay, I seem to have ssh-agent set up well enough that it runs. >However, it now complains: > >Agent parent directory is not sticky, mode is 40777 it should be 041777 > >To which directory is it referring? /tmp -- Joel "Espy" Klecker

Re: orig source

Hi! Carey Evans ([EMAIL PROTECTED]): > I've gotten the impression that the best way to do it is to use > *pristine* uptream source, which means that the .orig.tar.gz is really > the tar file you downloaded. The changes should all be in the > (automatically generated) .diff.gz. Does this also app

Building "sublanguages" from gcc

Hello, I have the hang of building a package with deb-make and build scripts, but I've run into a snag. I'm attempting to package the latest version of gpc (gpc-980405) but it wants to be built from the gcc directory. You can't start build in the gpc subdirectory (/gcc-2.8.0/p). Manually runni

Re: One source, two binary packages

-BEGIN PGP SIGNED MESSAGE- On 8 Apr 1998, Ben Gertzfield wrote: > Here's the debian/rules from my GIMP packages. It should clear up > your confusion. It uses debhelper judiciously; I'd recommend using > debhelper to save your sanity. :) > > #!/usr/bin/make -f > > # First, we build the p

Re: orig source

Jeff Shilt <[EMAIL PROTECTED]> writes: > Is the original, exactly the way I got it, or can I remove the > other OS specific directories, fix all the makefiles and have this be the > original source. I've gotten the impression that the best way to do it is to use *pristine* uptream source, w

Re: orig source

-BEGIN PGP SIGNED MESSAGE- On Wed, 8 Apr 1998, Jeff Shilt wrote: > I'm working on packaging FPK-pascal compiler, and I was was > wondering what exactly is meant by the original source. The sources for > fpc come with source for linux, dos, amiga, etc. Plus, the makefiles in > the

Re: One source, two binary packages

Manoj Srivastava <[EMAIL PROTECTED]> writes: > I have this in my directory on master (rules.tar.gz, I > think). README follows (the tarball has HTML stuff in it too, meant > to be dropped onto the develoers corner web page). You should just put this up on the public HTML space on master..

Re: One source, two binary packages

Hi, I have this in my directory on master (rules.tar.gz, I think). README follows (the tarball has HTML stuff in it too, meant to be dropped onto the develoers corner web page). manoj __ Here are a set

Re: One source, two binary packages

Ben Gertzfield <[EMAIL PROTECTED]> writes: > Your debian/rules should build *both* packages. > > Here's the debian/rules from my GIMP packages. It should clear up > your confusion. It uses debhelper judiciously; I'd recommend using > debhelper to save your sanity. :) Bob, don't fear the reaper.

Re: closing old bugs

James Troup <[EMAIL PROTECTED]> writes: > Hugo Haas <[EMAIL PROTECTED]> writes: > > On Thu, 9 Apr 1998, Damjan Marion wrote: > > > Can someone tell me what I must do to close old bugs, after > > > uploading new upstream version. I am a new maintainer of that > > > package. > > > > To close bug#n

Re: One source, two binary packages

Your debian/rules should build *both* packages. Here's the debian/rules from my GIMP packages. It should clear up your confusion. It uses debhelper judiciously; I'd recommend using debhelper to save your sanity. :) #!/usr/bin/make -f # First, we build the package. The automake/aclocal/autoconf s

One source, two binary packages

I am preparing my first package, and am building it by hand to get a clearer understanding of the package building process. It will have two binary packages, dictd and dict, both of which come from the dictd source. I have reached the point where the first, and larger, package produces