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

Re: Scythe in Debian Med Git



Hi Andreas,

On 08:18 11/05, Andreas Tille wrote:
> Hi Kevin,
>
> please note that I'm forwarding my answer to the list.  I would always
> advise to send questions like yours to the list since it enhances your
> chances to get an answer more quickly.  Please always remember that
> Debian Med is a team and not a single person.

Apologies, I absent-mindedly replied to you personally again. I'll endeavour to
group-reply in future.

<snip>
> > I've added a get-orig-source rule to d/rules, which wgets a tarball using the
> > github API. This tarball is specific to the git SHA hash of upstream's current
> > master, which defined version 0.994 (i.e., will always download the same
> > content, even if upstream's master changes). I hope this is acceptable.
>
> As a temporary solution until upstream might be convinced to do proper
> releases this is OK.  It also serves for others as documentation how we
> obtained the tarball.

OK, I'll leave it as is until Vince gets back to me about tagging a released
version.

<snip>

> To the package itself:  I did a couple of minor changes and commited
> these.  It would have been more work to describe what you should do than
> doing it quickly myself.  Please check the log thoroughly.  There is one
> remaining issue:  You are creating the manpage at build time but the
> result is quite poor regarding line spacing etc.  It also adds a ruby
> build-dependency.  Could you please preprocess the manpage and commit it
> right to the debian/ dir after checking that the syntax is OK?

OK, I have made a new and improved d/scythe.1 and removed the ronn-based system
(including from build-depends, and d/rules). Is it worth doing something
similar with the README.html which we now generate, to avoid a build-dep on
python-markdown?

Cheers,
Kevin

---
Kevin Murray

GPG pubkey: http://www.kdmurray.id.au/static/A4B4EE6A.asc
FPR: 656C 0632 1EAB 2C3F 3837  9767 17C2 8EB1 A4B4 EE6A


Reply to: