On Sunday 11 March 2007 15:01:27 Steve Long wrote: > > I don't know what you mean by making Portage recognize the software > > installed this way. Do you want Portage to be able to uninstall and/or > > upgrade this software? If so, the simple answer is you it can't do > > that. You have to manage the software outside of Portage yourself.
He can if he makes an ebuild for it (or as Neil suggested finds one outside the tree). It's not that hard to do. > [...] package.provided - I used this for that kde-env script that was moved > last year, as certain pkgs in the tree still depended on its ebuild, but it > had been moved to kde-libs (which it blocked.) I unmerged it to get > kde-libs, and put an entry in package.provided for pkgs which still had a > dependency on it. Once the tree had all been updated I deleted the entry. package.provided is certainly not intended to be used to circumvent dependencies due to blocks. Not that that has any relevance to this thread though. -- Bo Andresen
pgpPU35n4Ljry.pgp
Description: PGP signature
