From: lewis@sistina.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Debian packaging
Date: Thu, 14 Dec 2000 10:46:41 -0600 [thread overview]
Message-ID: <20001214104641.A15193@sistina.com> (raw)
In-Reply-To: <0012132115222N.00826@lyta>; from russell@coker.com.au on Wed, Dec 13, 2000 at 09:15:22PM +0100
[-- Attachment #1: Type: text/plain, Size: 3861 bytes --]
On Wed, Dec 13, 2000 at 09:15:22PM +0100, Russell Coker wrote:
> I plan to take over the Debian package of lvm because the current maintainer
> hasn't fixed serious bugs for quite a while.
A couple of questions. Have you tried contacting Tom Lees <tal26@cam.ac.uk>? I have talked to him and he is working on LVM 0.9 packages for sure. Has this transfer of maintainers been approved by the powers that be at Debian yet?
> I have created packages for lvm 0.8.1 and lvm 0.9. One change I think should
> be done is an option for ./configure to specify whether a shared library
> should be used or whether the programs should be statically linked. If this
> is desired then someone please tell me which version I should create a patch
> against and I'll send it in.
Since the configure.in scripts are essentially the same, you can just submit a
patch to one or the other to the lvm-devel list and we'll get it in on the
next release. I am the one responsible for the conversion of LKM to the autoconf system, so I'd be interested to see how you intend to accomplish this.
> Also as part of the Debian packaging I have put the following patch in to
> make it clean up all files after compiling:
> diff -ruN ../LVM.orig/lvm-0.8.1.orig/Makefile.in lvm-0.8.1-0/Makefile.in
> --- ../LVM.orig/lvm-0.8.1.orig/Makefile.in Sun Nov 12 19:52:12 2000
> +++ lvm-0.8.1-0/Makefile.in Wed Dec 13 15:40:06 2000
> @@ -39,4 +39,5 @@
> distclean: clean
> $(MAKE) -C tools distclean
> rm -f config.cache config.log config.status
> - rm -f Makefile make.tmpl
> + rm -f Makefile make.tmpl tools/Makefile tools/tools_and_lib.make.tmpl
> \
> + tools/lib/Makefile tools/man8/Makefile
>
> Also I have put in the following patch to work with the way Debian packages
> have different compile and install directories:
> --- ../LVM.orig/lvm-0.8.1.orig/make.tmpl.in Sun Nov 12 19:52:12 2000
> +++ lvm-0.8.1-0/make.tmpl.in Wed Dec 13 15:40:06 2000
> @@ -35,11 +35,16 @@
> # Setup directory variables
> prefix = @prefix@
> exec_prefix = @exec_prefix@
> -bindir = @bindir@
> -sbindir = @sbindir@
> -libdir = @libdir@
> -infodir = @infodir@
> -mandir = @mandir@
> +bindir = ${PREFIX}@bindir@
> +sbindir = ${PREFIX}@sbindir@
> +libdir = ${PREFIX}@libdir@
> +infodir = ${PREFIX}@infodir@
> +mandir = ${PREFIX}@mandir@
> +
> +ifeq ($(TOP),)
> +TOP := $(shell cd `for i in . .. ../..; do if [ -f $$i/LVM-HOWTO ]; then
> echo $$i; break; fi; done`; pwd)
> +export TOP
> +endif
>
> # helper scripts
> UNINSTALL = ${TOP}/autoconf/uninstall.pl
Are you saying you want this patch applied to the upstream source? That
really doesn't make much sense to me. The Makefile.in patch is completely
unnecessary because the subdirectories Makefile.in files handle those
cleanups. And it doesn't make any sense to me to put the ${PREFIX} stuff in
the upstream version, as it is not necessary. That is what the
package.diff.gz file is created for when you build Debian packages. That way
when you make a new version, the changes you made to the source are applied to
the new code.
> Also I would prefer to have the Debian packaging files in the upstream
> source. They are about 5K of data in 11 files in a separate sub-directory.
> Please let me know if this would be desired/accepted as part of the LVM
> upstream source and I will send the relevant patch to you.
One question. Why? Seems completely unnecessary to me.
Regards,
--
AJ Lewis
Sistina Software Inc. Voice: 612-379-3951
1313 5th St SE, Suite 111 Fax: 612-379-3952
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
No-one suspects the butterfly!
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-12-14 16:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 20:15 [linux-lvm] Debian packaging Russell Coker
2000-12-14 15:50 ` Tamas Gergely
2000-12-14 16:22 ` Russell Coker
2000-12-17 2:00 ` Ragnar Kjørstad
2000-12-17 10:49 ` Claudio Matsuoka
2000-12-17 9:47 ` Luca Berra
2000-12-17 18:00 ` Andreas Dilger
2000-12-18 1:00 ` Claudio Matsuoka
2000-12-19 20:24 ` Fionn Behrens
2000-12-19 22:51 ` Andreas Dilger
2000-12-20 8:43 ` Ulf Bartelt
2000-12-20 15:04 ` Claudio Matsuoka
2000-12-20 21:53 ` Russell Coker
2000-12-20 22:30 ` lewis
2000-12-20 23:15 ` Andreas Dilger
2000-12-14 17:43 ` HIBINO Kei
2000-12-15 17:58 ` Gergely Tamas
2000-12-15 22:10 ` Ragnar Kjørstad
2000-12-15 23:13 ` Jay Weber
2000-12-16 7:19 ` Gergely Tamas
2000-12-14 16:46 ` lewis [this message]
2000-12-15 6:51 ` Russell Coker
2000-12-15 18:15 ` lewis
2000-12-17 20:04 ` Tom Lees
-- strict thread matches above, loose matches on Subject: below --
2000-12-20 15:18 Claudio Matsuoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001214104641.A15193@sistina.com \
--to=lewis@sistina.com \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox