On Sep 10, Terry Hancock ([EMAIL PROTECTED]) wrote:
> Thanks for all the replies, this one brings up some related questions...
>
> On Tuesday 09 September 2003 07:55 pm, Neil Roeth wrote:
> > The approach I took with a multi-binary package that I created from scratch
> > was to do the configu
On Sep 10, Goedson Teixeira Paixao ([EMAIL PROTECTED]) wrote:
> * Neil Roeth ([EMAIL PROTECTED]) wrote:
> > The approach I took with a multi-binary package that I created from scratch
> > was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> > export it, and do the make
On Sep 10, Terry Hancock ([EMAIL PROTECTED]) wrote:
> Thanks for all the replies, this one brings up some related questions...
>
> On Tuesday 09 September 2003 07:55 pm, Neil Roeth wrote:
> > The approach I took with a multi-binary package that I created from scratch
> > was to do the configu
On Sep 10, Goedson Teixeira Paixao ([EMAIL PROTECTED]) wrote:
> * Neil Roeth ([EMAIL PROTECTED]) wrote:
> > The approach I took with a multi-binary package that I created from scratch
> > was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> > export it, and do the make
Thanks for all the replies, this one brings up some related questions...
On Tuesday 09 September 2003 07:55 pm, Neil Roeth wrote:
> The approach I took with a multi-binary package that I created from scratch
> was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> export it,
* Neil Roeth ([EMAIL PROTECTED]) wrote:
> The approach I took with a multi-binary package that I created from scratch
> was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> export it, and do the make install. This puts everything into the directory
> hierarchy below debian
Thanks for all the replies, this one brings up some related questions...
On Tuesday 09 September 2003 07:55 pm, Neil Roeth wrote:
> The approach I took with a multi-binary package that I created from scratch
> was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> export it,
* Neil Roeth ([EMAIL PROTECTED]) wrote:
> The approach I took with a multi-binary package that I created from scratch
> was to do the configure and make, then set DESTDIR to $(CURDIR)/debian/tmp,
> export it, and do the make install. This puts everything into the directory
> hierarchy below debian
On Sep 9, Terry Hancock ([EMAIL PROTECTED]) wrote:
> My immediate question:
> I need to build a dual binary (a runtime and a development)
> package from a single source package, called "wcstools",
> which I am creating with dh_make and dpkg-buildpackage.
>
> I've seen various references to
On Sep 9, Terry Hancock ([EMAIL PROTECTED]) wrote:
> My immediate question:
> I need to build a dual binary (a runtime and a development)
> package from a single source package, called "wcstools",
> which I am creating with dh_make and dpkg-buildpackage.
>
> I've seen various references to
On Tuesday 09 September 2003 02:34 pm, Terry Hancock wrote:
> My immediate question:
Um, I'm reading the debhelper man page -- is it possible
that this is as simple as using the "m" option on dh_make
and then naming all the control files wcstools.rules,
wcstools-dev.rules, etc (i.e. foo -> pack
On Tuesday 09 September 2003 02:34 pm, Terry Hancock wrote:
> My immediate question:
Um, I'm reading the debhelper man page -- is it possible
that this is as simple as using the "m" option on dh_make
and then naming all the control files wcstools.rules,
wcstools-dev.rules, etc (i.e. foo -> pack
* Terry Hancock ([EMAIL PROTECTED]) [030909 21:56]:
> I've seen various references to how these should be "built
> in debian/wcstools and debian/wcstools-dev" instead of
> just in "debian/tmp" -- but I *haven't* found out how to
> make that happen. Is there something else I should be
If you us
My immediate question:
I need to build a dual binary (a runtime and a development)
package from a single source package, called "wcstools",
which I am creating with dh_make and dpkg-buildpackage.
I've seen various references to how these should be "built
in debian/wcstools and debian/wcstools-dev
* Terry Hancock ([EMAIL PROTECTED]) [030909 21:56]:
> I've seen various references to how these should be "built
> in debian/wcstools and debian/wcstools-dev" instead of
> just in "debian/tmp" -- but I *haven't* found out how to
> make that happen. Is there something else I should be
If you us
My immediate question:
I need to build a dual binary (a runtime and a development)
package from a single source package, called "wcstools",
which I am creating with dh_make and dpkg-buildpackage.
I've seen various references to how these should be "built
in debian/wcstools and debian/wcstools-dev
16 matches
Mail list logo
