From: Junio C Hamano <junkio@cox.net>
To: Simon Richter <sjr@debian.org>
Cc: git@vger.kernel.org
Subject: Re: Regarding: Debian: packaging updates.
Date: Tue, 08 Nov 2005 11:30:21 -0800 [thread overview]
Message-ID: <7vbr0vey42.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 4370EEF7.4060708@debian.org
Simon Richter <sjr@debian.org> writes:
> I'm currently in the process of working my way through the current
> packaging, and there is quite a lot I am going to simplify. As the
> Debian build scripts do not expect this file to be autogenerated, I
> think it would be counterproductive to do so; it can seriously affect
> reproducability of builds.
>
> (actually, I would like to ask not to fix things in the Debian packaging
> that aren't broken, as providing an upgrade path for earlier versions
> will be a lot less painful then)
Noted. I just barely speak enough deb to build binary packages,
and the source packaging and upload procedure are something I've
never bothered to learn, so I won't be touching that area from
now on.
Since you have debian.org e-mail address, perhaps you can feed
me patches to debian/ area and deb: rule in the main Makefile?
I was asked to use dpkg-buildpackage/dpkg-genchanges and produce
the *.changes file as well by somebody who maintains his own
private apt source. I'd appreciate if you can take care of it
when you update the Makefile deb: rule as well, if the *.changes
file request makes sense to you.
next prev parent reply other threads:[~2005-11-08 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 17:08 Regarding: Debian: packaging updates Johannes Schindelin
2005-11-08 18:31 ` Simon Richter
2005-11-08 19:30 ` Junio C Hamano [this message]
2005-11-08 19:36 ` Simon Richter
2005-11-09 23:06 ` Junio C Hamano
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=7vbr0vey42.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sjr@debian.org \
/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;
as well as URLs for NNTP newsgroup(s).