Re: new lmodern package
Hi Florent! Hi Frank!
Long email, answer to 4 other emails ...
On Fre, 10 Feb 2006, Florent Rougon wrote:
> ,----
> | The dependencies and conflicts they define must be satisfied (as
> | defined earlier for binary packages) in order to invoke the targets in
> | `debian/rules', as follows:[1]
> |
> | `Build-Depends', `Build-Conflicts'
> | The `Build-Depends' and `Build-Conflicts' fields must be
> | satisfied when any of the following targets is invoked: `build',
> | `clean', `binary', `binary-arch', `build-arch', `build-indep' and
> | `binary-indep'.
> |
> | `Build-Depends-Indep', `Build-Conflicts-Indep'
> | The `Build-Depends-Indep' and `Build-Conflicts-Indep' fields must
> | be satisfied when any of the following targets is invoked:
> | `build', `build-indep', `binary' and `binary-indep'.
> `----
>
> When clean is run, Build-Depends-Indep is *not* guaranteed to be
> satisfied. However, Build-Depends is.
On Fre, 10 Feb 2006, Frank Küster wrote:
> Because dh_clean is in debhelper which is not build-essential.
>
> I didn't look at what lintian says, but I guess the right solution would
> be to put debhelper into Build-Depends, and the rest in Build-Depends
> indep.
Ok, with this lintian shuts up. And everyone is content? In svn.
> > Yes, it should be >= 0.10
Changed in svn.
On Fre, 10 Feb 2006, Florent Rougon wrote:
> > Defnitely, I haven't checked the defoma stuff at all, the list is AFAIR
> > automatically generated.
>
> I am not sure I understand you correctly. debian/lmodern.defoma-hints
> was *not* automatically generated in lmodern <= 0.92-11. However,
> lmodern.scale and lmodern.fontlist-x11 are generated from
> lmodern.defoma-hints.
I took your lmodern.defoma-hints and added automatically generated hints
for the missing/new fonts in lmodern-0.99.3, at least AFAIR.
Automatically generated means with the use of defoma-hints
> > Misunderstanding of Map vs MixedMap.
> >
> > MixedMap only tells you that there are pk sources and type1 sources.
> >
> > Since we have
> > dvipsPreferOutline true
> > in updmap.cfg normally the type1 sources are used. Furthermore, the maps
> > in these config files are *NOT* activated.
> >
> > If we would write Map instead of MixedMap, nobody would ever again be
> > able to use the cmr pk fonts, even if he tells dvips that he does not
> > wan to have type1 fonts!
>
> But this happens only if the Map (currently MixedMap) lines in the
> replacement .cfg files are uncommented by the user. If the user
> uncomments the line with lm-rep-cmtext.map in 10lmodern-cm.cfg, it means
> he wants LM used in place of CM, doesn't it? I'd say even when using PK
> fonts, and even when dvipsPreferOutline is false. My reasoning is that
> when uncommenting the line, the user means: "I want LM used whenever CM
> should be used". Maybe you think he means instead "I want LM used
> whenever CM-Type 1 should be used"?
Well for me the "original" are the cmr pk fonts. Then there are
replacement fonts in type1 format. I can replace the bitmap fonts with
type1 fonts of cmr, or lmr, or whatever, but I don't replace the bitmap
fonts.
> > Florent, do you want to have write access to the lmodern svn repo, i.e
> > pkg-texlive svn?
>
> Yes, please. Thanks.
Done. If you check out the stuff from
svn://svn.debian.org/pkg-texlive/lmodern
please note that I use svn-buildpackage and that the property
mergeWithUpstream is set (see svn-buildpackage manual). So create a
directory lmodern/tarballs and put lmodern-0.99.3.orig.tar.gz into it,
after this svn-buildpackage -us -uc -rfakeroot etc should merge the
debian dir into the orig.tar before building.
On Fre, 10 Feb 2006, Frank Küster wrote:
> Florent Rougon <f.rougon@free.fr> wrote:
>
> > Also, a few minor comments about debian/copyright:
> >
> > - You chose to include the GUST Font Source License in
> > debian/copyright. This is OK, but I think it would cause less work
> > for future upstream releases to install the
> > doc/fonts/lm/GUST-FONT-SOURCE-LICENSE.txt file provided by upstream
> > into /usr/share/doc/lmodern and simply point to this file from
> > debian/copyright. That way, you don't have to check every time there
> > is a new upstream release that GUST-FONT-SOURCE-LICENSE.txt didn't
> > change in the meantime.
>
> I don't know whether ths is policy compliant - instead I think the
> license text *must* be in the copyright file. I suggest to rename the
> copyright file to copyright.Debian and generate the copyright file in
> debian/rules by
>
> cat debian/copyright.Debian doc/fonts/lm/GUST-FONT-SOURCE-LICENSE.txt > debian/copyright
Implemented.
> > - I see no other reference to the GNU GPL than the following two lines
> > in debian/copyright:
> >
>
> What licensing do we choose for the Debian packaging part? Even if we
Please READ the copyrightfile!!!!!
Debian packaging
----------------
Copyright (c) 2004 Florent Rougon
Copyright (c) 2005 Norbert Preining
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2 dated June, 1991.
...
Open things:
- MixedMap vs. Map
- do we wait for tex-common 0.16
Comments?
(For all changes see svn).
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining AT logic DOT at> Università di Siena
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
HUNA (n.)
The result of coming to the wrong decision.
--- Douglas Adams, The Meaning of Liff
Reply to: