On Sat, Jul 28, 2001 at 03:46:17AM +0100, Will Newton wrote:
> dh_installdirs --package=otcl1 --tmpdir=./debian/tmp
> dh_installdirs --package=otcl-dev --tmpdir=./debian/tmp
>
> # Add here commands to install the package into debian/tmp
> install -d debian/tmp
>
I have uploaded an updated version of my public key to
keyring.debian.org (I just attended the key signing party at OLS).
Unfortunately, the output of finger for my e-mail address at debian.org
still displays my old key.
The Developer's Reference states that there is some delay, which I
assumed wa
On Saturday 28 July 2001 3:20 am, Joshua Haberman wrote:
> If your source package creates more than one binary package and the
> upstream Makefile installs everything at once, then debian/tmp and
> dh_movefiles are useful. But otherwise debian/ is easiest.
It seems I can get the package to build
* Will Newton ([EMAIL PROTECTED]) wrote:
> On Saturday 28 July 2001 2:33 am, Ben Collins wrote:
>
> > Why not make the change in debian/rules rather than in the package's
> > Makefile?
> >
> >
> > install -d debian/tmp
> > $(MAKE) install DESTDIR=$(PWD)/debian/tmp
> >
> > Should do the tri
On Sat, Jul 28, 2001 at 03:46:17AM +0100, Will Newton wrote:
> dh_installdirs --package=otcl1 --tmpdir=./debian/tmp
> dh_installdirs --package=otcl-dev --tmpdir=./debian/tmp
>
> # Add here commands to install the package into debian/tmp
> install -d debian/tmp
>
On Saturday 28 July 2001 2:33 am, Ben Collins wrote:
> Why not make the change in debian/rules rather than in the package's
> Makefile?
>
>
> install -d debian/tmp
> $(MAKE) install DESTDIR=$(PWD)/debian/tmp
>
> Should do the trick.
This way I have to manually create all dirs under de
On Sat, Jul 28, 2001 at 01:24:21AM +0100, Will Newton wrote:
>
> I've been trying to create my first debian package following the New
> Maintainers Guide, and I've run into a problem. The guide mentions that
> binaries should be installed to ./debian/tmp and then dh_movefiles will move
> them a
I have uploaded an updated version of my public key to
keyring.debian.org (I just attended the key signing party at OLS).
Unfortunately, the output of finger for my e-mail address at debian.org
still displays my old key.
The Developer's Reference states that there is some delay, which I
assumed w
I've been trying to create my first debian package following the New
Maintainers Guide, and I've run into a problem. The guide mentions that
binaries should be installed to ./debian/tmp and then dh_movefiles will move
them as necessary to the correct destination. Unfortunately, while the
desti
On Saturday 28 July 2001 3:20 am, Joshua Haberman wrote:
> If your source package creates more than one binary package and the
> upstream Makefile installs everything at once, then debian/tmp and
> dh_movefiles are useful. But otherwise debian/ is easiest.
It seems I can get the package to build
* Will Newton ([EMAIL PROTECTED]) wrote:
> On Saturday 28 July 2001 2:33 am, Ben Collins wrote:
>
> > Why not make the change in debian/rules rather than in the package's
> > Makefile?
> >
> >
> > install -d debian/tmp
> > $(MAKE) install DESTDIR=$(PWD)/debian/tmp
> >
> > Should do the tr
On Saturday 28 July 2001 2:33 am, Ben Collins wrote:
> Why not make the change in debian/rules rather than in the package's
> Makefile?
>
>
> install -d debian/tmp
> $(MAKE) install DESTDIR=$(PWD)/debian/tmp
>
> Should do the trick.
This way I have to manually create all dirs under d
On Sat, Jul 28, 2001 at 01:24:21AM +0100, Will Newton wrote:
>
> I've been trying to create my first debian package following the New
> Maintainers Guide, and I've run into a problem. The guide mentions that
> binaries should be installed to ./debian/tmp and then dh_movefiles will move
> them
I've been trying to create my first debian package following the New
Maintainers Guide, and I've run into a problem. The guide mentions that
binaries should be installed to ./debian/tmp and then dh_movefiles will move
them as necessary to the correct destination. Unfortunately, while the
dest
On Thu, Jul 26, 2001 at 11:08:50PM +1000, Sam Couter wrote:
> > Or maybe MS could get out of the habit of hiding file extensions.
>
> ... but those file extension thingys are just too confusing! How am I
> supposed to know what they mean? The computer should just do what I want!
s/I want/M\$ want
On Thu, Jul 26, 2001 at 11:08:50PM +1000, Sam Couter wrote:
> > Or maybe MS could get out of the habit of hiding file extensions.
>
> ... but those file extension thingys are just too confusing! How am I
> supposed to know what they mean? The computer should just do what I want!
s/I want/M\$ wan
On Thu, Jul 26, 2001 at 11:08:50PM +1000, Sam Couter wrote:
> I don't think the warning that macros could be virii actually achieves
> anything. Users just hit the "Yeah, whatever" button and get infected
> anyway. Hitting those buttons becomes a reflex with no thought at all.
Well, at least they
On Thu, Jul 26, 2001 at 11:08:50PM +1000, Sam Couter wrote:
> I don't think the warning that macros could be virii actually achieves
> anything. Users just hit the "Yeah, whatever" button and get infected
> anyway. Hitting those buttons becomes a reflex with no thought at all.
Well, at least they
18 matches
Mail list logo
