Re: new lmodern package
Norbert Preining <preining@logic.at> wrote:
> Ok, with this lintian shuts up. And everyone is content? In svn.
FWIW, I can live with that. :-)
> 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
OK, understood.
> 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.
OK, that is a possible interpretation of the DviPSPreferOutline
semantics...
> 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.
I never use svn-buildpackage, but you said the build can be done
normally after exporting the SVN tree, so it's OK. I nevertheless keep
your hint under my pillow.
>> > - 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
> ----------------
[...]
Yes, sorry. As I said to Frank, I forgot that part when I checked!
> Open things:
> - MixedMap vs. Map
I think there are two possible interpreations to the DviPSPreferOutline
semantics, and I don't care much which one is chosen.
> - do we wait for tex-common 0.16
That I cannot comment on.
> Comments?
No more. Well, yes. I suppose we cannot filter the commit messages from
pkg-texlive that refer to lmodern and not to the rest of texlive. Too
bad...
--
Florent
Reply to: