patch fails in ebuild, not by hand

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

I'd like to have an ebuild download say, mirror://gentoo//gcc-core-${SOMEVERSION}.tar.bz2 but if it isn't present on any mirrors, have that satisfied by downloading (either through emerge or with a fetch restriction) http://vendor.org/downloads/gcc_with_a_different_name.tgz

Anyone know how to do this?
see below for the current patch issue

[n00b@localhost] · Posted: Thu Jan 27, 2011 8:31 pm Post subject:

I don't think you can currently.

If a file is present on a vendor's website with a particular name, it should also have that name on all the gentoo mirrors. Emerge will automatically try all the mirrors and if it can't find the file on any revert to downloading from the vendor's website.

I am struggling to see where this would be useful. Could you give an example?

phajdan.jr · Posted: Thu Jan 27, 2011 8:50 pm Post subject:

I think you can download the file manually and put it inside /usr/portage/distfiles with a different name.
_________________
http://phajdan-jr.blogspot.com/

Mousee · Posted: Thu Jan 27, 2011 8:56 pm Post subject:

If you modify the ebuild yourself and toss it into a local overlay, or if you're just creating an ebuild for an app not in portage already, you would just set the SRC_URI (in the ebuild) to whatever upstream's download URI is ("http://vendor.org/downloads/gcc_with_a_different_name.tgz" in your example). The ebuild will first attempt to fetch from upstream and, if that fails, check the gentoo mirrors next.

Otherwise if you're trying to do this for packages in portage without modifying them as I explained above - then I'm unaware of any method for doing so, and I'm fairly certain one doesn't exist as you'd still have to have a coded SRC_URI for upstream, which not all packages have (several fetch purely from the mirrors).

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

the reason is I need core gcc stuff to add in ada.
1. gcc-core-X.X.X is less than half the size of regular gcc <- current way its done
2. if a given gcc-core doesn't exist I'd like to revert to the vendor gcc package, or the full blown gcc which should still work <- fall back if there is no core, however probably the better way anyway... less tarballs to maintain

[n00b@localhost] · Posted: Thu Jan 27, 2011 11:00 pm Post subject:

If I understand you correctly could you not just create a gcc-core ebuild and have gcc-ada depend on either like

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

Genone · Posted: Fri Jan 28, 2011 8:23 pm Post subject:

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

Is there any reason why a patch command, executed exactly is listed in the enviroment file of the portage tmp dir, would work, where it fails during the emerge? Very strange behaviour. Some hunks succeed, some fail. Immediatly following the emerge failure, I can move into the temp dir and patch the file with out error. Any thoughts??

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

also, if I patch manually, zip up, and take the patch logic out of the ebuild, everything works flawlessly

redgsturbo · Apprentice Joined: 24 Jun 2005 Posts: 283

no joy?

currently if you install gnat-gcc, it downloads the appropriate gcc-core, and then adds gcc-ada, patches, and builds. emergeing gnat-gpl fetches a gcc/adacore ada source and patchset tarball already applied. This means more packages to distribute and maintain that aren't needed, and further, gnat-gpl's sources will apply to gcc-4.3 or gcc-4.5, the only difference being the gcc you fetch and the patches you apply. The modular design I'm working on is more efficient, and easer to maintain as the versions progress...

I already have a perfect gnat-gpl-4.3.6.2010, but I want to fix it right and then submit. But, I need help with this patching issue. Nothing in the logs, environment, or process are sticking out