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

Re: Debian package for PGF 2.10



Hi Faheem

2011/3/4 Faheem Mitha <faheem@email.unc.edu>:
>
> I'm not entirely clear what to do with your comments below. Should I work on
> this package some more and upload it somewhere? Should I file bugs against
> the Debian package? Something else?

I would convey your changes to Makoto.  I'm sure he's willing to add
your changes to his development tree and upload them in the next
release.

Adding an extra target in the debian/rules to automatically download
and package the version would improve the quality of the PGF package.
Whenever the upstream package releases something new, it's easy for
both the maintainer and regular users to retrieve the latest upstream
package and start working on it.

> On Mon, 28 Feb 2011, Danai SAE-HAN (韓達耐) wrote:
>
>> 2011/2/27 Faheem Mitha <faheem@email.unc.edu>:
>>>
>> If you build the package with something like a "get-orig-source"
>> target, then you will always have this issue.  You can add a "chmod
>> -x" in the debian/rules, and later on ask upstream to remove the
>> executable bit.
>
> Ok. Just stick a
>
> chmod -x filename
>
> in the rules file?

That would solve the problem, indeed.  Meanwhile, ask upstream to
remove the executable bit on their source.  In the next upstream
release you won't have to insert the "chmod -x" anymore.

>> You could add some attributes like how thorough and beautifully
>> written the documentation is.  That's one of the first things that
>> impressed me when I looked at PGF and TikZ.
>> Most documents are boring and technical, but this guide has a nice
>> introduction, large reference material, etc.  Add something that
>> compels end users to download the manual.
>
> It's true. The TikZ/PGF is most excellent, and PGF represents an improbable
> amount of high quality work.
>
> How about
>
> Document: pgf
> Title: User s Guide to the PGF Package, Version

No genitive " s ".  Just "User guide to the PGF package"

> Author: Till Tantau <tantau@cs.tu-berlin.de>
>
> Abstract: This is a comprehensive and high quality manual for PGF and TikZ,
> including several tutorials and a detailed reference. It discusses both the
> more accessible frontend subsystems such as TikZ, and more low-level and
> powerful functionality that may not be needed by the average user.
>
> Section: Text
>
> (With feedback from
> http://chat.stackexchange.com/rooms/41/tex-latex-and-friends)

Looks fine to me!

>>> However
>>>
>>> texdoctk pgf
>>>
>>> does not work.
>>>
>>> Running just
>>>
>>> texdoctk
>>>
>>> and then searching for pgf brings up a window, but when I click on it I
>>> get
>>> an error. So I must have done something wrong here.
>>
>> I believe there was a discussion a long time ago about the differences
>> between texdoc and texdoctk.  texdoc is the one used by TeX Live; I
>> don't know if texdoctk is still actively maintained, but was used with
>> teTeX.  Try "texdoc -s pgf" to get some results in a terminal.
>
> Yes, texdoc works as you described. Is texdoctk supposed to work or not?

I don't think so.  It's just there for legacy reasons, I suppose.


Cheers


-- 
Danai


Reply to: