On Mon, Nov 01, 2021 at 09:24:29PM +, Kerry wrote:
> I get a binary .deb in the parent directory of my application directory.
> I would like to change this so that all .debs are placed in a different
> directory so I tried overriding 'dh_builddeb' in 'rules':
d/rules is a wrong place for this,
'dh_builddeb' in 'rules':
override_dh_builddeb:
mkdir ./deb_package
dh_builddeb --destdir=./deb_package
This successfully puts the package in the desired directory but the next stage
of the packaging fails:
dh_gencontrol
dpkg-gencontrol: warning: unknown information field &#x
fix it?
>
> It looks like you're installing (from upstream) directly into
> debian/glimpse...
>
> debhelper, however, defaults to running make install
> DESTDIR=debian/$(PACKAGE) when the source package builds only one binary
> package.
>
> So, you have a few optio
directory (or whereever you've told it to look using --sourcedir).
debhelper, however, defaults to running make install
DESTDIR=debian/$(PACKAGE) when the source package builds only one binary
package.
So, you have a few options:
1. Override the default dh_auto_install rule to pass
On Mon, 11 Nov 2013 12:11:53 -0800, Russ Allbery wrote:
> Upstream doesn't appear to support DESTDIR in their build system and is
> just trying to install things directly under prefix. You can possibly
> work around this by setting prefix to $(CURDIR)/debian/tmp, but this
>
On Tue, Jan 10, 2012 at 10:56 PM, Andreas Rönnquist
wrote:
> I am making a package (which I am upstream of) translatable using
> gettext - It is using a simple Makefile as build system, no autotools.
>
> Is there a way to come around the necessity to get LOCALEDIR (Which
> is basi
Hi!
I am making a package (which I am upstream of) translatable using
gettext - It is using a simple Makefile as build system, no autotools.
Is there a way to come around the necessity to get LOCALEDIR (Which
is basically ${DESTDIR}{$prefix}/share/locale) from the Makefile to
the C source?
In
ot;/usr/local/bin/b43-fwcutter":
> Permission denied
> make[1]: *** [install] Error 1
>
> Why is it installing under /usr/local, anyway? In the upstream Makefile you
> should replace
>
>PREFIX ?= /usr/local
>
> with
>
>PREFIX ?= $(DESTDIR)/usr
Le Monday 11 August 2008 01:37:52 John G. Heim, vous avez écrit :
> The program I'm working on uses a configure script to build a Makefile. So
> I need to change it to install the binary into /usr/bin instead of
> /usr/local/bin. But the new maintainer's guied says to put $(DES
l/bin. But the new maintainer's guied says to put $(DESTDIR) in
front of the directory names. Like:
BIN = $(DESTDIR)/usr/bin
But the Makefile already uses that variable name. What is the point of using
$(DESTDIR) in maintaining the Makefile?
--
To UNSUBSCRIBE, email to [
Justin Pryzby wrote:
It _used to_ be the case that it was an environment variable set (and
exported) by ./debian/rules, but then people realized that under this
configuration, debhelper would behave differently when run by the
makefile than it would when run manually (for testing, debugging,
Timo Steuerwald:
> >Timo Steuerwald:
> >>I try to create packages for sipX from sipfoundry.org. This is a PBX
> >>like asterisk and is composed of a few subprojects like sipXportLib,
> >>sipXtackLib...
> >>I now tried to create a package for sipXportLib.
> >Firstly, you should know that ./debian/
libs,
nothing. The same for the -dev package: No documentation, include files
and so on.
If I look now to the debian subdirectory, there are three subdirectories
tmp (which is my DESTDIR in the rules file), sipxportlib and
sipxportlib-dev. The last two only contain the same files as in the
packages.
You may want to read it. E.g. dh_install is copying files
from your source directory into the directory where the Debian package
will be built. And there is a file like debian/$PACKAGE.install which
lists files installed by dh_install.
> If I look now to the debian subdirectory, there are
o on.
> If I look now to the debian subdirectory, there are three subdirectories
> tmp (which is my DESTDIR in the rules file), sipxportlib and
> sipxportlib-dev. The last two only contain the same files as in the
> packages. What can I do to add the files from DESTDIR to the two
&
the
debian subdirectory (like usr/share/doc/sipxportlib/copyright). No libs,
nothing. The same for the -dev package: No documentation, include files
and so on.
If I look now to the debian subdirectory, there are three subdirectories
tmp (which is my DESTDIR in the rules file), sipxportlib and
On Sun, 2005-04-10 at 14:18 +0200, jano kupec wrote:
> Hi there,
>
> the application i'm packaging uses qmake to generate the Makefile. But
> qmake uses its own DESTDIR variable (which points to where the binary
> target should go), so it conflicts with DESTDIR used by
Hi there,
the application i'm packaging uses qmake to generate the Makefile. But
qmake uses its own DESTDIR variable (which points to where the binary
target should go), so it conflicts with DESTDIR used by
dpkg-buildpackage.
How can i get around this?
I invoke qmake in debian/rules conf
Hello Sven,
* Sven Mueller <[EMAIL PROTECTED]> [2005-03-23 15:30]:
> Nico Golde wrote on 22/03/2005 20:04:
> >Isn't DESTDIR obsolete, if the script understands prefix?
> >regards nico
>
> Not necessarily. Many source Packages (read: upstream source) understand
&
Nico Golde wrote on 22/03/2005 20:04:
Isn't DESTDIR obsolete, if the script understands prefix?
regards nico
Not necessarily. Many source Packages (read: upstream source) understand
prefix, but only take that into account for binaries (and use a
different one for data files or man
an-mentors/2004/07/msg00392.html)
> >
> > Even when using
> > DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(DEB_DESTDIR)
> > I had no sucess.
>
> This should work, but are you sure the upstream Makefile of your package
> understands DESTDIR? If not you should patc
7; directory in the last part
| of your install invocation.
| Quoting your diff:
|
| /usr/bin/install -s -m 755 bin/ali2gff $(DESTDIR)/bin/
|^^^
|
|>>- why not using /usr/bin/install for everything when copying files,
it has
|>Because there i
are on bin/ directory.
yes but you're already mentioning the 'bin' directory in the last part
of your install invocation.
Quoting your diff:
/usr/bin/install -s -m 755 bin/ali2gff $(DESTDIR)/bin/
^^^
> >- why not using /usr/bin/instal
les are perl scripts.
Install says something about not possible to strip the perl files.
last but not least you could set up DESTDIR this way:
INSTALLDIR = $(DESTDIR)$(LBIN)
at the beginning of the Makefile, then you can forget it :) then either
use /usr/bin/install as said above or leave the original
Hubert Chan wrote:
"Nelson" == Nelson A de Oliveira <[EMAIL PROTECTED]> writes:
Nelson> #!/usr/bin/make -f
Nelson> DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes
Nelson> DEB_DESTDIR = $(CURDIR)/debian/gff2aplot
Nelson> DEB_MAKE_CLEAN_TARGET:= clean
Nelson> DEB_MAKE_IN
>>>>> "Nelson" == Nelson A de Oliveira <[EMAIL PROTECTED]> writes:
Nelson> #!/usr/bin/make -f
Nelson> DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes
Nelson> DEB_DESTDIR = $(CURDIR)/debian/gff2aplot
Nelson> DEB_MAKE_CLEAN_TARGET:= clean
Nelson> DEB_MAKE_I
On Tue, Mar 22, 2005 at 01:45:25PM -0300, Nelson A. de Oliveira wrote:
> Hi
>
> Arjan Oosting wrote:
> >Op di, 22-03-2005 te 12:04 -0300, schreef Nelson A. de Oliveira:
[...]
> Since it doesn't have DESTDIR, I have created a patch (available here:
> http://biolinux.df.i
Hi
Sven Mueller wrote:
The original Makefile is available here:
http://biolinux.df.ibilce.unesp.br/naoliv/cdbs/Makefile
Since it doesn't have DESTDIR, I have created a patch (available here:
http://biolinux.df.ibilce.unesp.br/naoliv/cdbs/01-makefile.diff)
Your Patch adds DESTDIR support t
.html)
Even when using
DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(DEB_DESTDIR)
I had no sucess.
This should work, but are you sure the upstream Makefile of your package
understands DESTDIR? If not you should patch the upstream Makefile.
Maybe you could send the upstream Makefile so we can have a look
:= install DESTDIR=$(DEB_DESTDIR)
I had no sucess.
This should work, but are you sure the upstream Makefile of your package
understands DESTDIR? If not you should patch the upstream Makefile.
Maybe you could send the upstream Makefile so we can have a look?
OK.
The original Makefile is available here
_TARGET := install DESTDIR=$(DEB_DESTDIR)
> I had no sucess.
This should work, but are you sure the upstream Makefile of your package
understands DESTDIR? If not you should patch the upstream Makefile.
Maybe you could send the upstream Makefile so we can have a look?
Greetings Arjan Oosting
sign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nico,
|>#!/usr/bin/make -f
|>
|>DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes
|>DEB_DESTDIR = $(CURDIR)/debian/gff2aplot
|>DEB_MAKE_CLEAN_TARGET:= clean
|>DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(DEB_DESTDIR)
prefix=$(DEB_DESTDIR)
Hello Nelson,
* Nelson A. de Oliveira <[EMAIL PROTECTED]> [2005-03-22 12:05]:
[...]
> #!/usr/bin/make -f
>
> DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes
> DEB_DESTDIR = $(CURDIR)/debian/gff2aplot
> DEB_MAKE_CLEAN_TARGET:= clean
> DEB_MAKE_INSTALL_TARGET := insta
ke install DESTDIR=/tmp":
cp bin/ali2gff /tmp/bin/
cp: cannot create regular file `/tmp/bin/ali2gff': No such file or directory
make: *** [installbin] Error 1
It is getting the DESTDIR variable OK. So I think that the problem is not om
the Makefile.
My debian/rules is this:
[sorry for the AOL re: DH_COMPAT mode 3 and dh_installdeb]
also sprach Justin Pryzby <[EMAIL PROTECTED]> [2005.03.09.0036 +0100]:
> If a file is provided by the package, then it is a conffile and
> not only a configuration file.
Yes.
> OTOH, if maintainer scripts create the file (possibly from
>
also sprach Justin Pryzby <[EMAIL PROTECTED]> [2005.03.08.2315 +0100]:
> Yes. This makes it a "configuration file". If you want it to be a
> conffile (which I suspect you do), you should also list it in
> debian/conffiles.
This is actually not necessary if you use dh_installdeb. Since
DH_COMPAT
On Tue, Mar 08, 2005 at 08:11:24PM -0300, Lucas Wall wrote:
> On 03/08/2005 07:15 PM, Justin Pryzby wrote:
> >On Tue, Mar 08, 2005 at 11:02:19PM +0100, Rakotomandimby (R12y) Mihamina
> >wrote:
> >>2 )
> >>
> >>To install the configuration file, I append to what I written (in the
> >>"inst
On 03/08/2005 07:15 PM, Justin Pryzby wrote:
On Tue, Mar 08, 2005 at 11:02:19PM +0100, Rakotomandimby (R12y) Mihamina wrote:
2 )
To install the configuration file, I append to what I written (in the
"install" section yet:
cp minimalist.conf-sample debian/minimalist/etc/minimalist.co
On Tue, Mar 08, 2005 at 11:02:19PM +0100, Rakotomandimby (R12y) Mihamina wrote:
> Hello,
> I'm still learning to build debian package.
> Following the Debian New Maintainer's guide.
> There are two things I dont understand:
>
> 1 ) ---
> I want that once the binary package is installed, the f
Hello,
I'm still learning to build debian package.
Following the Debian New Maintainer's guide.
There are two things I dont understand:
1 ) ---
I want that once the binary package is installed, the file
'minimalist.pl' is into '/usr/bin'. To do so, I put these in the install
section of my "ru
On Tue, 2004-12-07 at 23:39 +0100, Nico Golde wrote:
> > I am trying to create a .deb file. If i do not change
> > the rules, it create the correct .deb file. However,
> > when i changed DESTDIR=/usr/tmp, it install all
> > the stuff in /usr/tmp correctly, however did not
also sprach Yan <[EMAIL PROTECTED]> [2004.12.08.0209 +0100]:
> I am trying to create a .deb file. If i do not change
> the rules, it create the correct .deb file. However,
> when i changed DESTDIR=/usr/tmp, it install all
> the stuff in /usr/tmp correctly, however did not
>
Hello Yan,
* Yan <[EMAIL PROTECTED]> [2004-12-07 23:36]:
> Hi:
> I am trying to create a .deb file. If i do not change
> the rules, it create the correct .deb file. However,
> when i changed DESTDIR=/usr/tmp, it install all
> the stuff in /usr/tmp correctly, however did not
&
Hi:
I am trying to create a .deb file. If i do not
change
the rules, it create the correct .deb file.
However,
when i changed DESTDIR=/usr/tmp, it install
all
the stuff in /usr/tmp correctly, however did not
include those in the .deb.
Anyone can help?
THANKS.
Yan
Hi all,
I am trying to package an internally used perl module for distribution
amongst servers. This works well. The package builds and installs fine.
The problem arises when I try to use the --destdir instruction with
dh_builddeb. I would like the package to be available in my repository
after
Hi all,
I am trying to package an internally used perl module for distribution
amongst servers. This works well. The package builds and installs fine.
The problem arises when I try to use the --destdir instruction with
dh_builddeb. I would like the package to be available in my repository
after
* Pratik Sinha <[EMAIL PROTECTED]> [010803 13:38]:
> what changes do i need to make to the Makefile of a package with respect to DESTDIR??
>
> why does one need to make this changes??
(I'm not a Debian Developer, but an aspiring one)
You are not forced to change the Makef
what changes do i need to make to the Makefile of a package with respect to DESTDIR??
why does one need to make this changes??
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Pratik Sinha <[EMAIL PROTECTED]> [010803 13:38]:
> what changes do i need to make to the Makefile of a package with respect to
> DESTDIR??
>
> why does one need to make this changes??
(I'm not a Debian Developer, but an aspiring one)
You are not forced to change the Ma
what changes do i need to make to the Makefile of a package with respect to
DESTDIR??
why does one need to make this changes??
--
f the document is 0.6 or lower, please
go to http://www.debian.org/~elphick/manuals.html/maint-guide/
> But it seems to me that the DESTDIR doesn't work.
> Is there a mistake in the Makefiles or have I misunderstood
> something of the build process.
You missed one important part,
l, parallel or distributed executing real world applications.
The Concurrent Clean Programming Development System is a special
programming environment for Concurrent Clean.
---debian/control end---
But it seems to me that the DESTDIR doesn't work.
Is there a mistake in the Makefiles or have
On Tue, Dec 15, 1998 at 05:40:40PM +0900, Ionutz Borcoman wrote:
> # Add here commands to compile the package.
> $(MAKE) MY_DEBIAN_SYSTEM=1
> This way I get as much freedom as I want:
> a. non-Debian users just give a make from the top dir.
> b. Debian users give just dpkg-buildpackag
Hamish Moffatt wrote:
>
> On Tue, Dec 15, 1998 at 03:18:52PM +0900, Ionutz Borcoman wrote:
> > How do I set the DESTDIR in my Makefile ? If a non-debian user will
> > download the package, he/she will want to install my program in
> > /usr/local. If he/she is a debian user
On Tue, Dec 15, 1998 at 03:18:52PM +0900, Ionutz Borcoman wrote:
> How do I set the DESTDIR in my Makefile ? If a non-debian user will
> download the package, he/she will want to install my program in
> /usr/local. If he/she is a debian user, the deb package should be
> created from th
Hi,
How do I set the DESTDIR in my Makefile ? If a non-debian user will
download the package, he/she will want to install my program in
/usr/local. If he/she is a debian user, the deb package should be
created from the tar.gz and files moved to completely different places,
like /etc, /usr/X11R6
56 matches
Mail list logo
