Thanks for your suggestion. I think the following way > You could have texlive-texmf *just* > "Replaces" it, and then supply an updated tetex-texmf that is empty > and just specifies "Depends:texlive-texmf".
is a good solution, if Fink officially employs TeX Live and drops teTeX, with the permission of the maintainer of tetex*. Tomoaki Okayama P.S. Also thanks for the detailed explanation about Provides. It also troubled me a lot, and that is the main reason why the virtual package "tetex3-base" was introduced in tetex.info and ptex.info. See also http://article.gmane.org/gmane.os.apple.fink.devel/12420 http://article.gmane.org/gmane.os.apple.fink.devel/12629 At Sun, 11 Oct 2009 18:53:31 +0000 (UTC), Daniel E. Macks wrote: > > Tomoaki Okayama <okay...@sodan.ecc.u-tokyo.ac.jp> said: > > > > I am pleased to announce that TeX Live is now available on > > 10.4/10.5/10.6 in unstable. Enjoy it! > > Thank you for working on this! > > Problem on 10.4/ppc, all up-to-date unstable as of a few days ago: > > % fink update libkpathsea4 > > The following package will be built: > libkpathsea4 > The following additional package will be installed: > texlive-texmf > > While trying to install: > texlive-texmf-0.20080822-1 > > The following inconsistencies found: > Unsatisfied dependency in tetex-base: tetex-texmf (>= 3.0-1) > > Trying to resolve dependencies... > Could not resolve inconsistent dependencies! > > Fink isn't sure how to install the above packages safely. You may be able to > fix things by running: > > fink scanpackages > sudo apt-get update > sudo apt-get install texlive-texmf=0.20080822-1 > > > Doing that fails with: > texlive-texmf: Conflicts: tetex-texmf > > > It's a bug in the whole way texlive tries to be compatible with tetex: > "Provides" do not contain versioning information, so a dependency that > specifies a version can never be satisfied by a Provides. Because > there are packages that have versioned dependencies on tetex-texmf, > that must continue to exist as a real package itself. > > A further or more general technical issue is that a > Provides/Replaces/Conflicts for a certain name never works like you > expect if the given name is also a real package. That's an intentional > (to Debian) limit or distinction between a Provides item vs a Package > item. > > I do not know anything about tex, but this sounds like a standard > obsolete/renamed package situation. Does texlive-texmf supply the same > program-names as tetex-texmf did? You could have texlive-texmf *just* > "Replaces" it, and then supply an updated tetex-texmf that is empty > and just specifies "Depends:texlive-texmf". That's the standard way to > migrate to a new package-name for the same or updated contents. > > dan > > -- > Daniel Macks > dma...@netspace.org > http://www.netspace.org/~dmacks > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
