On Thu, 2005-10-11 at 20:51 -0600, Brian Harring wrote: > On Thu, Nov 10, 2005 at 06:42:54PM -0800, Brian wrote: > > Just a quick question. With all the changes I see in this list. Is > > there anything coming (that you know of) that will break porthole's use > > of portage. > Long term? I'm unfortunately looking at breaking pretty much all api > access portage wise, for 3.0.
I knew that one. From what I have gathered so far I believe 3.0 is getting the long awaited public API. Is that correct? If so I'll have to start paying more attention to it and setup a test box to start changing our portagelib.py to use it. (I can't afford to trash my main box, I have business stuff on it.) Just let me know when it's time for testing. :) > > Short term? Unless you're doing questionable stuff like bypassing the > cache layer and accessing the files on disk... nope, shouldn't hork > anything. > > ~harring mostly just lookup stuff, get defaults, status, package info, etc.. All emerges are done properly through a terminal and normal command line calls. Thanks... -- Brian <[EMAIL PROTECTED]> -- [email protected] mailing list
