[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#322091: Bluefish

On Ter, 2005-08-23 at 23:14 +0200, Daniel Leidert wrote:
> Never seen this practice before. And it can be problematic, if you think
> about the practice of handling outdated
> automake/autoconf/intltool/gettext scripts/files. One possibility to
> handle this situation is, that the necessary applications are run once
> in the upstream source _before_ beginning the packaging process. So the
> scripts can be updated without increasing the size of the diff.gz. In
> this case, your practice will always fail.

You shouldn't need to run anything other than './configure && make &&
make install' (with a few tweaks) on a recently extracted tarball to
install it system-wide.
Automake/autoconf/intltool/etc, should be run _prior_ to release, and
shouldn't be outdated (but if they are, that's an upstream problem, not
Debian, even though we can - and some times should - work around it).

The original tarball generates a perfect package with very simple
changes, take a look at:
You can download the dsc, diff and changes files from this site and the
tarball from upstream and run 'dpkg-source -x bluefish_1.0.3-1.dsc'.
It's clean, simple and cruft-free[1]. 
And already has you set up as the maintainer.

BTW, since you have upstream access, it would be a good idea to remove
the Debian dir from releases, as soon as possible.


[1] The debian directory only needs these files: README.Debian,
bluefish.manpages, compat, copyright, rules, bluefish.1, changelog,
control, patches.
The rest is left-over from upstream, since diff doesn't handle deleted
files (illustrating another good reason not to have the /debian dir


 Leo Antunes
 <costelaaa@ig.com.br> | <costela@debian.org> | <costela@gmail.com>

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: