Re: latex-cjk upload to unstable ...
'ello!
From: Frank Küster <frank@debian.org>
> Danai SAE-HAN (韓達耐) <danai.sae-han@skynet.be> wrote:
>
> > Hi!
> >
> > I've created a single manpage for all the *latex scripts in CJK. You
> > find it attached to this email. I hope it's okay.
> >
> >
> > About the error trapping, I tried to get it working with variable
> > targets (like I did in latex-cjk-chinese-arphic), but that proves too
> > much of a hassle for my little computer brain.
> >
> > I think I have a much simpler solution: a comment where to find the
> > output.
> >
> > # You can find a log of what's happening in build/log.
> > cd build; \
> > ./wftodm -FontBase dg wadalab-sym/jis*.ps wadalab-gothic-0-13/goth-*.ps > log 2>&1 && \
> > ./wftodm -FontBase dm wadalab-sym/jis*.ps wadalab-mincho-0-12/min-*.ps >> log 2>&1 && \
> > ./wftodm -FontBase mc wadalab-sym/jis*.ps wadalab-mincho-0-8/min-*.ps >> log 2>&1 && \
> > ./wftodm -FontBase mr wadalab-sym/jis*.ps wadalab-maru-0-8/maru-*.ps >> log 2>&1
> >
> > If any of the commands in debian/rules fails, it will output it anyway.
>
> Hm, I didn't look into the rules file again (I think I've deleted it on
> my disk). But in any case it is important that if the build fails, the
> contents of the log file are automatically displayed. This is important
> if one encounters a problem while using pbuilder (which will then remove
> the whole chroot), or even more if an official buildd fails.
Hmmm, I didn't think about that: the user can't sniff the logs if
pbuilder fails. Bummer.
There are two reasons why I first redirected the output into log files
instead of on-screen. First was that there is so much information
that it makes it difficult to follow what's happening exactly.
Secondly and more importantly, when the scripts are bursting out so
much information, it would slow (my) computer even more because my
terminal couldn't follow, temporarily hijacking my CPU.
So there are two easy solutions:
(1) either I won't redirect it anymore, or I will redirect it to the
screen as well (it's not that many people will build the package
themselves, I suspect). This option carries my favour;
(2) or I could redirect the output to a file in /tmp. If I would
choose this last way, do I need to name the logs with $RANDOM in
the filename (Debian policy doesn't say anything about it, but I
have noticed that quite a few packages do this)? Or can I call it
anything I like? And would you suggest to delete the logfile
after the last successful command?
A less elegant way would be to put an if clause around every command.
> As for the man page, i think it's very good. Only two minor issues:
>
> .SH AUTHOR
> - The under section \fBNAME\fP mentioned programs were written by
> Werner
> + The programs mentioned in section \fBNAME\fP were written by Werner
> Lemberg <wl@gnu.org>.
> .PP
> This manual page was written by Danai SAE-HAN <danai.sae-han@skynet.be>,
> for the Debian project (but may be used by others).
Heh, sorry. I'm used to write in legalese. ;D
> And you should extend the last sentence with a real license statement,
> something like "It is in the public domain and may be freely used,
> distributed and/or modified", or alternatively the GPL or whatever if
> you prefer.
OK. Now it looks like this:
.PP
This manual page was written by Danai SAE-HAN <danai.sae-han@skynet.be>
for the Debian project. It is licensed under the GNU General Public
License version 2 or higher, of which you can find a copy online at
http://www.gnu.org/licenses/gpl.txt or on Debian systems under
/usr/share/common-licenses/GPL-2 (part of the "base-files" package).
(Ralph'ish) Cheerio!
Danai SAE-HAN
韓達耐
--
题目:《元日》
作者:王安石（１０２１－１０８６）
爆竹声中一岁除，春风送暖入屠苏。
千门万户［日童］［日童］日，总把新桃换旧符。
Reply to: