On Thu, 2005-10-27 at 08:26 +0900, Jason Stubbs wrote:
On Thursday 27 October 2005 08:04, m h wrote:
Hmmm, then I must be missing where the spec file gets generated,
because there is no code in ebuild.py that does it...
ebuild.py..? Are you using 2.1.0_alphayymmdd? You may very well be the only
person trying to use rpm with that version. Try dropping back to 2.0.53 and
see what happens there.
If I may chime in. Our rpm support is a tad incomplete currently. I've
got some patches which overhaul the rpm handling in portage that come
from Peter S. Mazinger so portage can properly generate usable rpm's
without requiring user interaction etc. It's $FEATURE based and I've got
about 135 packages built from it in my local tree. I think Peter has
some 500+ working ones.
http://dev.gentoo.org/~solar/patch_overlay/sys-apps/portage/
portage-*rpm*.patch
The package rpm itself in portage needs some love, which is why these
really patches have not been submitted to bugzilla/portage-dev yet.
Before this support can really work properly we have to find a
maintainer for the rpm package and get him/her the patches to allow us
to have /usr/src/gentoo and gentoo-like configurations. Originally only
redhat/mandrake/suse/conectiva compatible packages were supported. We
have some PIC corrections, corrections from openpkg, allow to bootstrap
into packaging, and better handling of shared/debug/rpc allow to use
newer beecrypt and system provided popt corrections from openpkg.
Peter anything I'm forgetting to mention about this?
You have to subscribe to the mailing list to reply.
--
Ned Ludd [EMAIL PROTECTED]
--
gentoo-portage-dev@gentoo.org mailing list