Brian Harring wrote:
On Thu, Apr 07, 2005 at 01:02:26PM +0100, Ciaran McCreesh wrote:We have no control over what Apple will do for a 10.3 -> 10.4 upgrade which is why IMHO the smokes and mirrors with paths is the best option. You can't go replacing primary OSX files with GNU ones and expect everything to be fine when OSX can fex. overwrite GNU sed with it's own version upon upgrade, or security release or whatnot. Then the user is screwed. I would expect similar behavior on BSD. Portage is not the primary handler of the system and it shouldn't try to be. --
On Thu, 7 Apr 2005 06:04:03 -0500 Brian Harring <[EMAIL PROTECTED]>
wrote:
| You know apple ain't going to support the broken mess that results, | and nor will we most likely. That is why we can't go replacing | whatever we label as broken[1] on *any* system where portage is | secondary.
Then we can't support portage as a secondary package manager.
Well, since you say so... :P
One note, stating that gentoo osx no longer functions with portage as a secondary pkg manager still doesn't do jack for addressing the 10.3 -> 10.4 issue... so really, it still is secondary.
~brian
--
gentoo-dev@gentoo.org mailing list
gentoo-dev@gentoo.org mailing list
