Maxim Veksler wrote: > On 4/30/07, Lior Kaplan <[EMAIL PROTECTED]> wrote: >> Maxim Veksler wrote: >> > P.S, OT, btw, foo-msg and co. >> > This whole thing it to get subversion v1.4, which for some reason >> > (bad!) has does have rpm for RH4 but no .deb for Debian 3.1/Ubuntu >> > 6.10. This in turn to enable me seeing meld diff of a checkouted >> > source on the RH4 box (using svn1.4) from on a mapped via sshfs folder >> > in my Ubuntu 6.10 laptop. Meld FYI can automagically detect that you >> > are diffing from an svn directory and display you those diffs (local >> > copy vs. HEAD revision). >> >> subversion 1.4.2 is the version in debian stable (= Etch), testing and >> unstable at the moment. See >> http://packages.debian.org/stable/devel/subversion >> >> You can find a backport from 1.4.2 to oldstable (= Sarge or 3.1) at >> http://www.backports.org/debian/pool/main/s/subversion/ >> >> It was done by the same debian maintainer... >> >> Enjoy. >> > > Thanks for helping Lior :) > > Yhea, I know the new shiny Debian "stable" has svn 1.4. That helps, > and I could probably take the backport and use it on my Ubuntu 6.10 > and it will work as well. Great (I've started the upgrade by now so > guess I'll just let it run). > > The fact I'm more curies about though is that you as a Debian > developer don't have a straight answer to my main question in this > email. Is what I'm asking such a exotic request? Please don't get me > wrong, there is not a inch of complaint in this reply it's that I'm > amazed that such a simple request can't be answered with "apt-magic > repository php5-gd".
I do think it's an exotic request, and the reason is that it's not in APT's responsibilities. Apt should manage software installation and removal, which it does based on your installed packages, and your *current* repositories. What you're asking needs information also on *past* repositories. Lets look at unstable, in which packages come and go relatively quick. It mean, that if I don't update daily, I can find myself with installed packages which currently doesn't exist in the repository. From where should apt take the info about the source repository? On a more technical side: When you create a package, you do that regardless of any repository, so there isn't any meta data about that. Before installation APT (and aptitude) will resolve the package dependencies and download the .deb files. From there, the installation is done with DPKG, which doesn't know anything about repositories. Same as you would have done the installation manually with DPKG. I hope this answer is enough. Please let me know if you want more info. > Anyway, I've started looking at the issue. It seem that the real horse > behind apt is libapt (/usr/lib/libapt-pkg-libc6.3-6.so.3.11.0). I > can't seem to able to find any documentation for the API. $ apt-cache show libapt-pkg-doc [snip] Description: Documentation for APT development This package contains documentation for development of the APT Debian package manipulation program and its libraries. Enjoy. -- Lior Kaplan [EMAIL PROTECTED] http://www.Guides.co.il ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
