| 1 |
To re-direct you one more time, maybe have a look over at the |
| 2 |
gentoo-portage-dev list. That's where portage development happens. We |
| 3 |
just use it. :) |
| 4 |
|
| 5 |
We are in the process of making gentoo's portage work on osx as a |
| 6 |
secondary package manager (as you put it earlier). We ideally use / as |
| 7 |
the root. Much of what we've push into portage mainline (as bug |
| 8 |
reports) has to do with using POSIX versions of tools rather than the |
| 9 |
gnu versions. This has to do with portage code as well as ebuilds |
| 10 |
themselves. the gentoo/bsd group also does this with their work. Both |
| 11 |
of our projects are focused on getting portage running on non-linux |
| 12 |
systems. There was talk of gentoo/open solaris as well. |
| 13 |
|
| 14 |
I don't think I fully understand what you're looking for, but I hope you |
| 15 |
find it :) |
| 16 |
|
| 17 |
Cheers, |
| 18 |
-Nick Dimiduk |
| 19 |
|
| 20 |
m h wrote: |
| 21 |
> Hello- |
| 22 |
> |
| 23 |
> I posted in the gentoo-dev mailing list yesterday, but figured I'd post |
| 24 |
> here since it is somewhat closer related. I'm investigating the |
| 25 |
> differences between portage and openpkg. For those who don't know about |
| 26 |
> openpkg, openpkg allows one to install rpms in a sandboxed environment |
| 27 |
> accross multiple unix platforms (bsd, redhat, debian, gentoo,...). It |
| 28 |
> consists of a way to bootstrap an environment and a bunch of spec files |
| 29 |
> used to create rpms specifically tailored for that platform. The idea |
| 30 |
> being you could run the "same" components across different platforms in |
| 31 |
> your environment. |
| 32 |
> |
| 33 |
> It seems that Fink and Portage for OSX are providing similar |
| 34 |
> functionality on top of OSX. My question is what would be involved in |
| 35 |
> generalizing the Portage OSX port to unix platforms similar to what |
| 36 |
> openpkg is doing. An example might be that while I need to run Suse at |
| 37 |
> work, I could install portage into a sandboxed location and enter that |
| 38 |
> environment. This would allow me to run newer components, better |
| 39 |
> integrated, security patched, etc, while still having the corporate |
| 40 |
> environment if I needed it. |
| 41 |
> |
| 42 |
> Ideally the benefits for doing this would be to allow many platforms to |
| 43 |
> take advantage of portage, use the large ebuild tree (openpkg has ~400 |
| 44 |
> components), as well as use ebuilds that are tested probably a little |
| 45 |
> bit more than openpkg (I believe the gentoo install base is a least one |
| 46 |
> or two orders of magnitude larger than openpkg). |
| 47 |
> |
| 48 |
> Any thoughts, comments, or suggestions are appreciated. |
| 49 |
> |
| 50 |
> thanks |
| 51 |
> |
| 52 |
> matt |
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-osx@g.o mailing list |
Archives