| Summary: | Ebuild: dev-libs/root-4.00.08 (was: dev-libs/root-4.00.06a) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Hypnos <hypnos75> |
| Component: | New packages | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | bicatali |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://root.cern.ch/root/Availability.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dev-libs/root-4.00.06a.ebuild
root-4.00.06a.ebuild root-4.00.08.ebuild root-4.00.08f.ebuild |
||
|
Description
Hypnos
2004-06-30 14:26:04 UTC
Created attachment 34518 [details]
dev-libs/root-4.00.06a.ebuild
Changes from dev-libs/root-3.10.02-r1 :
* sh kung fu to handle patch sources
* Support for new Python module
phosphan, looks like you're the maintainer, please add a metadata.xml file reflecting that Well, I don't consider myself the maintainer just because I did one version bump and one bugfix, but this obviously fits for the sci herd. However, this beast needs some patching to survive gcc 3.4... In portage - thanks! I missed something in my Python support -- /usr/lib/root must be in the PYTHONPATH. So src_install should be changed from
---------------
src_install() {
make DESTDIR=${D} INSTALL="install" install || die "install failed"
dodir /etc/env.d
echo > ${D}/etc/env.d/99root "LDPATH=\"/usr/lib/root\""
}
----------------
to
-----------------
src_install() {
make DESTDIR=${D} INSTALL="install" install || die "install failed"
dodir /etc/env.d
echo > ${D}/etc/env.d/99root "LDPATH=\"/usr/lib/root\""
if [ `use python` ]; then
echo "PYTHONPATH=\"/usr/lib/root\"" >> ${D}/etc/env.d/99root
fi
}
-----------------
I am attaching an ebuild with this revision.
Created attachment 35033 [details]
root-4.00.06a.ebuild
Perhaps it would be better to put the python stuff into site-packages instead of tweaking PYTHONPATH if that's possible. Assigning to the sci herd because I currently don't have much time. Well, that would be a little hackish and the ebuild already had tweaks to LDPATH. ROOT is a bit of a beast, so there's no perfectly clean way to install into a FHS-compliant tree until ROOT starts using autotools (or equivalent). attached subsequently is an ebuild for v4.00.08, the first 4.x release declared ready for "production" use. Changes from v4.00.06a: - Version bump - Ruby bindings in addition to Python bindings (keyed to USE words) Has passed my research group's (icecube.wisc.edu) build acid test .... Created attachment 35597 [details]
root-4.00.08.ebuild
I should add that the gcc-3.4 patch should no longer be necessary, but that
should be tested by someone running gcc-3.4 ...
Created attachment 40617 [details] root-4.00.08f.ebuild Corrected a bug in SRC_URI of root-4.00.08.ebuild, and added a possibility for inclusion of cernlib (which ebuild is in bug #65677), and thus a new USE flag. Is this the right way? root-4.02.00 now in Portage. |