TeXLive 2009 autoprovides/autorequires

Jindrich Novy jnovy at redhat.com
Thu Oct 8 09:36:16 UTC 2009


On Mon, Oct 05, 2009 at 01:20:02AM -0400, Ben Boeckel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Hi,
> 
> I upgraded to F12 recently and enabled the TeXLive 2009 
> packages. One thing that the massive split has created is that 
> package dependencies are not made at all. I had to manually 
> install some packages to satisfy some dependencies. I created 
> these (rudimentary) .prov and .req scripts (attached) to try and 
> kickstart something.

The upstream metadata do indeed contain incomplete dependecy
information. I'm not sure how upstream generates the metadata but it
makes sense to add dependencies present in STY files to the packages.

I'm not fan of adding a new texlive.prov/req to rpm. It is indeed a
general solution but it needs direct hacks and maintenance at rpm
side. We can take advantage of the fact that we actually have the
whole TeX distribution when packaging TeX Live so that I would rather
implement the STY dependency calculator to the TL package generator.

Maybe a good name for such deps would be tex-sty(foo) in order to
distinguish style dependencies from the others.

> 
> As they are, they don't do versioning yet (seems that some 
> packages do versioning with LaTeX commands) nor does it support 
> \RequirePackage being split over multiple lines (similar with 
> \ProvidesPackage). I also may not be handling all of the 
> possibilities of where the provides and requires information may 
> be in the files.

The versioning is tricky here as the description in the STY files is
available only in textual form with intention to parse it by brain and
not by script :)

Jindrich

> 
> - --Ben
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> 
> iQIcBAEBCAAGBQJKyYICAAoJEKaxavVX4C1XnjgQAOuvMB9WMhtkzN7h+IjHcRu2
> u4WFJRLVB4J/8zpPz/mxFbGIbeeJSjaUde+7oRuz2RV1jD9bC4P3sP4bRQN77Xrc
> ffC1lOI1X6S3+AQt/nUonJnmG0/vqdeILWp/AulBNngpzb7w50Kj3iWGg+Zws5gy
> tTDBCp9dZJNkXylqI6UNjduMghvI41p2md2l7cd1gzudmXvLWaZMDFBQ81OZJt1g
> RE5JBi7+1OkNfINEjShKg+o/SlllZvT4u5erHWy7Fb/rOUGPX7qbj9ZqwZaQNWqU
> Dpr/8TSrXmsiuKk7tr+jL+GAtdB+fx18ZDV4E3umvmqzG+0KzIj6WmuW/DEyotRs
> qdqryzxSeZwtTjScBHAQG+TWlkm9X24hjnKnbyqIRvT81hawxPI/e6RAXTuuDUl8
> R+53le3RG6/mMy7MDD6Aky1h37R+4uIpmNpIb7JaNHhtfRanROxUw1Ii1Fjh5d45
> qA8i2pWaHPRC3OEMhaIgTFO1yHSWC5uLZ75K0owWKVQzo/UqFNAJwlGdIefM4YHD
> mSGesiawXEMAK0Ggfy2YxcNYPfhErk6cy7vGS/TlQhouO6utJVkc/a4sjmZj7rlb
> 3EvpRn3M/YGqeWg9536I8L9ugVFDnEwq958DRznB0FKCVpycnph1zMofGviLkrVv
> vjL/wtA8bfitn/xgR24o
> =8Hkv
> -----END PGP SIGNATURE-----



> -- 
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list


-- 
Jindrich Novy <jnovy at redhat.com>   http://people.redhat.com/jnovy/




More information about the fedora-devel-list mailing list