From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>,
Daniel White <daniel@whitehouse.id.au>,
git@vger.kernel.org, stgit@packages.debian.org
Subject: Re: [StGit] Debian packaging update
Date: Thu, 28 Aug 2008 16:16:25 -0300 [thread overview]
Message-ID: <20080828191625.GA17955@khazad-dum.debian.net> (raw)
In-Reply-To: <20080828154128.GB13169@diana.vm.bytemark.co.uk>
On Thu, 28 Aug 2008, Karl Hasselström wrote:
> On 2008-08-28 11:09:29 -0300, Henrique de Moraes Holschuh wrote:
> > Whatever people told you guys, the sad truth is that for the
> > overwhelming majority of packages, the mere presence of a debian/
> > dir upstream is taken as a warning sign by any seasoned Debian
> > developer (i.e. it is so often a problem, we take it as a bad sign).
> > It almost never helps. I have no idea where stgit is in that regard,
> > though. And I have NOT checked the "upstream version of the Debian
> > packaging", so please don't take this personally.
> >
> > But I can tell you that most DDs would prefer that upstream dumped
> > the debian/ dir, unless it is kept *really* current. And really, at
> > that point, you are losing a lot of the benefits of a downstream
> > maintainer anyway (i.e. you are not delegating the whole issue to
> > him, so that you can ignore the packaging and just pay attention to
> > stgit itself).
> >
> > Of course, this changes a lot when upstream is also a Debian
> > developer and spends a few hours per week keeping up-to-date with
> > Debian policy and toolset changes, etc.
>
> So the optimal solution if we want to carry a debian/ directory (to
> allow users to easily build their own .debs, or whatnot) would maybe
> be to simply politely ask our Debian maintainer to send us patches or
> pull requests to keep it up-to-date?
Yes, but that assumes you release often. Otherwise users get an old
version of the packaging all the time.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-08-28 19:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 10:10 [StGit] Debian packaging update Daniel White
2008-08-21 22:35 ` Catalin Marinas
2008-08-22 13:51 ` Daniel White
2008-08-22 15:03 ` Daniel White
2008-08-22 21:52 ` Catalin Marinas
2008-08-22 21:57 ` Catalin Marinas
2008-08-23 3:58 ` Daniel White
2008-08-28 17:22 ` Sebastian Harl
2008-08-28 14:09 ` Henrique de Moraes Holschuh
2008-08-28 15:41 ` Karl Hasselström
2008-08-28 19:16 ` Henrique de Moraes Holschuh [this message]
2008-08-28 19:55 ` Yann Dirson
2008-08-28 19:24 ` Yann Dirson
2008-08-28 20:52 ` Yann Dirson
2008-08-28 22:27 ` Karl Hasselström
2008-08-30 22:33 ` Catalin Marinas
2008-08-31 7:00 ` Karl Hasselström
2008-08-30 22:36 ` Catalin Marinas
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=20080828191625.GA17955@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=catalin.marinas@gmail.com \
--cc=daniel@whitehouse.id.au \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=stgit@packages.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).