How do you upload/build sponsored packages?
Hi, When I sponsor a packages, I usually build it with : debuild -m'My Name [EMAIL PROTECTED]' But the .changes file looks like : Maintainer: My Name [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] I can see several sponsored packages whose .changes file look like: Maintainer: Sponsoree [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] How is this possible? Thanks. -- Jérôme Marant [EMAIL PROTECTED] [EMAIL PROTECTED] http://marant.org
Re: How do you upload/build sponsored packages?
Hi Jerome, I build like this: dpkg-buildpackge -rfakeroot -us -uc (actually, I use a little script called dbuild that tacks a $* on the end of the line in case I need to dbuild -sa) Once the packages builds correctly and I've reviewed it, I use debsign [EMAIL PROTECTED] changes file (actually, another list script, dsign, that contains) debsign [EMAIL PROTECTED] $* Hope that helps, tony On Thu, 22 May 2003, Jérôme Marant wrote: Hi, When I sponsor a packages, I usually build it with : debuild -m'My Name [EMAIL PROTECTED]' But the .changes file looks like : Maintainer: My Name [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] I can see several sponsored packages whose .changes file look like: Maintainer: Sponsoree [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] How is this possible? Thanks. -- Jérôme Marant [EMAIL PROTECTED] [EMAIL PROTECTED] http://marant.org
Re: How do you upload/build sponsored packages?
On Thu, May 22, 2003 at 05:01:54PM +0200, J?r?me Marant wrote: When I sponsor a packages, I usually build it with : debuild -m'My Name [EMAIL PROTECTED]' But the .changes file looks like : Maintainer: My Name [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] I can see several sponsored packages whose .changes file look like: Maintainer: Sponsoree [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] How is this possible? Use 'debuild -kyour name' instead (or, as I do, just use 'debuild -uc -us' and run debsign afterwards when I've checked that the build looks sane). -- Colin Watson [EMAIL PROTECTED]
Re: How do you upload/build sponsored packages?
On Thu, May 22, 2003 at 05:01:54PM +0200, Jérôme Marant wrote: When I sponsor a packages, I usually build it with : debuild -m'My Name [EMAIL PROTECTED]' But the .changes file looks like : Maintainer: My Name [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] I can see several sponsored packages whose .changes file look like: Maintainer: Sponsoree [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] How is this possible? By following the instructions given in developers' reference instead of the wrong ones given somewhere else. :-P Use use -kyourkeyid with debuild/dpkg-buildpackage instead of -m or build without signing (debuild/dpkg-buildpackage -uc -us) and sign afterwards with debsign. (Both debsign -m'My Name [EMAIL PROTECTED]' and debsign -kyourkeyid are ok.) cu andreas
Re: debconf problem
On 17/05/2003 Joey Hess wrote: $3 is empty, the previous version is in $2 Oh, thanks a lot ;) bye mejo -- Efficiency and progess is ours one more Now that we have the Neutron bomb It's nice and quick and clean and gets things done Kill kill kill kill kill the poor tonight
Re: How do you upload/build sponsored packages?
On Thu, May 22, 2003 at 06:13:17PM +0200, Andreas Metzler wrote: Use use -kyourkeyid with debuild/dpkg-buildpackage instead of -m or build without signing (debuild/dpkg-buildpackage -uc -us) and sign afterwards with debsign. (Both debsign -m'My Name [EMAIL PROTECTED]' and debsign -kyourkeyid are ok.) I actually don't see how dpkg-buildpackage's sign-immediately-after-build defaults ever make sense (except when dpkg-buildpackage was originally written, when debsign didn't yet exist). Why would you want to waste time signing a package you haven't tested yet? Surely the order should be build, test, sign. Accordingly, I have DEBUILD_DPKG_BUILDPACKAGE_OPTS=-uc -us, together with a bunch of other options that don't matter here, in ~/.devscripts. I've never yet found that I want the other behaviour. -- Colin Watson [EMAIL PROTECTED]
Re: libexecdir - helper scripts
Bill Moseley [EMAIL PROTECTED] writes:
On Tue, May 20, 2003 at 06:54:45PM +0100, Roger Leigh wrote:
[EMAIL PROTECTED] writes:
libexecdir='${exec_prefix}/lib/${PACKAGE}'
That's evil. The whole point of configure is to have install
locations standardised, and changing the defaults is never, ever,
a good idea.
The problem was the standard was ${exec_prefix}/libexec. Since I
run debian and I don't have /usr/libexec (or /usr/local/libexec) it
just wasn't standard in my world ;). My reading for FHS 4.7.1
seemed like /usr/lib is what I wanted.
True, but I presume you want it to be portable, and work on
distributions other than Debian, and OSes other than GNU/Linux.
I also remember searching google about libexecdir and finding mostly
heated discussion about libexecdir. In the end I was just more
comfortable with the Debian location.
As the author, that's your decision, but configure/automake are
supposed to let users decide where things go. You should always use
the autoconf defaults unless there is a compelling reason. In this
case, you are making it default to Debian-specific settings. As
Debian is a special case in this respect, and you can easily alter it
in debian/rules, I'd not do this myself.
I discussed this on the autoconf list and it was suggested we do in
cofigure.in:
AC_MSG_NOTICE([Setting libexecdir to \${exec_prefix}/lib/${PACKAGE}])
but again, that only happens if --libexecdir is *not* passed to
configure.
If you do do this, that's a good plan (though I don't recommend it).
Is there plan in Debian to use the standard /usr/libexec in the
future?
I'm not sure. The Hurd port already uses it; as for Linux ports, I
don't think it will in the near future, though I'd certainly like it
to be introduced in the medium term.
In debian/rules, just use ./configure --libexecdir=\$\{prefix\}/lib to
redefine it.
Can it be a dir within that?
--libexecdir=\$\{prefix\}/lib/swish-e
It can be whatever you like, but there's an easier approach (see
below)
I'd rather not clutter /usr/lib.
There's an easier way. In your Makefile.am, just do this:
pkglibexecdir = $(libexecdir)/$(PACKAGE)
and then
pkglibexec_PROGRAMS = foo
foo_SOURCES = foo.c foo.h bar.c bar.h
or
pkglibexec_SCRIPTS = foo
Now when you use --libexecdir=\$\{exec_prefix\}/lib, your directory will
become $(exec_prefix)/lib/$(PACKAGE). You can use plain $prefix
instead of $exec_prefix, but $exec_prefix is technically correct, and
usually they are the same.
Is there a reason why it can't be hard-coded in debian/rules?
./configure --prefix=/usr --libexecdir=/usr/lib/swish-e
Do as I suggest above, and then in debian/rules, do
./configure --prefix=/usr --libexecdir=\$${exec_prefix}/lib
(In this case, $exec_prefix == $prefix)
This keeps the configury stuff nice and generic, and you can still
customise it as you wish. Better still, it works exactly as people
will expect it to.
HTH,
Roger
--
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
Re: How do you upload/build sponsored packages?
Colin Watson [EMAIL PROTECTED] writes: On Thu, May 22, 2003 at 05:01:54PM +0200, J?r?me Marant wrote: When I sponsor a packages, I usually build it with : debuild -m'My Name [EMAIL PROTECTED]' But the .changes file looks like : Maintainer: My Name [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] I can see several sponsored packages whose .changes file look like: Maintainer: Sponsoree [EMAIL PROTECTED] Changed-By: Sponsoree [EMAIL PROTECTED] How is this possible? Use 'debuild -kyour name' instead (or, as I do, just use 'debuild -uc -us' and run debsign afterwards when I've checked that the build looks sane). Thanks. -- Jérôme Marant http://marant.org
Re: How do you upload/build sponsored packages?
Andreas Metzler [EMAIL PROTECTED] writes: How is this possible? By following the instructions given in developers' reference instead of the wrong ones given somewhere else. :-P I've not reread it lately. Use use -kyourkeyid with debuild/dpkg-buildpackage instead of -m or build without signing (debuild/dpkg-buildpackage -uc -us) and sign afterwards with debsign. (Both debsign -m'My Name [EMAIL PROTECTED]' and debsign -kyourkeyid are ok.) Thanks. -- Jérôme Marant http://marant.org
Re: libexecdir - helper scripts
On Thu, May 22, 2003 at 07:41:33PM +0100, Roger Leigh wrote: There's an easier way. In your Makefile.am, just do this: pkglibexecdir = $(libexecdir)/$(PACKAGE) and then pkglibexec_PROGRAMS = foo foo_SOURCES = foo.c foo.h bar.c bar.h I considered that, but didn't go that route because that means $(PACKAGE) always gets appended to libexecdir so you cannot completely override with --libexecdir. That's why I ended up changing the default for libexecdir. I'll discuss it more with our developers. Perhaps your suggestion above is the best way to go. Thanks for your time, -- Bill Moseley [EMAIL PROTECTED]
