From: Helmut Wollmersdorfer <helmut@wollmersdorfer.at>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: 0.7.6 release tomorrow...
Date: Wed, 24 Nov 2004 14:25:04 +0100 [thread overview]
Message-ID: <41A48BB0.4080707@wollmersdorfer.at> (raw)
In-Reply-To: <873bz2tiuk.fsf@wide.bouthors.org>
Cyril Bouthors wrote:
> On 19 Nov 2004,
>>It was told me before. But I will continue to maintain it for my own
>>(possibly other's) convenience. [With 'maintain' I mean to take the
>>official debian/ directory and to put it intdo DRBD's SVN.]
> Sure, I understand that the debian/ directory is useful for SVN users,
> it has to be kept in for them but is it necessary to distribute it in
> the tarballs?
See the thread with subject "0.7.5 release tomorrow..." around 2004-10-06.
The convenient way is to do "make tarball" before "dpkg-buildpackage
..." and "make-kpkg ...". And I never really understood the
module-assistant, even after nearly a day of studying the docs. Same is
true for the newer packaging stuff.
So, what's easier:
1) change and test the drbd/make plus writing a new "HOWTO build debian
packages from SVN/tarball", and test the HOWTO under different conditions.
OR
2) rm debian/ by debian maintainers
Helmut Wollmersdorfer
next prev parent reply other threads:[~2004-11-24 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 21:59 [Drbd-dev] 0.7.6 release tomorrow Philipp Reisner
2004-11-16 13:22 ` Philipp Hug
2004-11-16 14:12 ` Philipp Reisner
2004-11-17 19:32 ` Philipp Reisner
2004-11-18 7:16 ` Lars Ellenberg
2004-11-19 12:52 ` [Drbd-dev] " Cyril Bouthors
2004-11-19 14:12 ` Philipp Reisner
2004-11-22 7:59 ` Cyril Bouthors
2004-11-24 13:25 ` Helmut Wollmersdorfer [this message]
2004-11-24 13:46 ` Philipp Hug
2004-11-24 14:18 ` Philipp Reisner
2004-11-24 15:04 ` Philipp Hug
2004-11-24 22:21 ` Lars Ellenberg
2004-11-24 23:40 ` Philipp Hug
2004-11-25 0:57 ` Lars Ellenberg
2004-11-25 7:46 ` Cyril Bouthors
2004-11-19 15:39 ` Helmut Wollmersdorfer
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=41A48BB0.4080707@wollmersdorfer.at \
--to=helmut@wollmersdorfer.at \
--cc=drbd-dev@lists.linbit.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