| Summary: | sys-libs/gdbm-1.8.3-r4 installs files outside the prefix $EPREFIX | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daa Jaa <dREPLACEeLETTEReEjBYeLETTEReA> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | heroxbd, prefix |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | patch to $PORTDIR/sys-libs/gdbm/gdbm-1.8.3-r4.ebuild | ||
|
Description
Daa Jaa
2013-05-30 09:34:20 UTC
I have similar patches for : sys-devel/bison/bison-2.4.3.ebuild sys-devel/binutils/files/binutils-2.22-mint.patch sys-devel/binutils/binutils-2.23.51.0.8.ebuild sys-apps/portage/portage-2.2.01.21864.ebuild eclass/kernel-2.eclass dev-lang/python/python-2.7.3-r3.ebuildn dev-lang/perl/perl-5.12.4-r1.ebuild app-admin/eselect-python/eselect-python-20111108.ebuild Please tell me, here or by e-mail, if these patches, all related to prefix, are welcomed in https://bugs.gentoo.org, and if I should file a new bug for each of them. Comment on attachment 349634 [details, diff] patch to $PORTDIR/sys-libs/gdbm/gdbm-1.8.3-r4.ebuild why do you care about gdbm-1.8.x ? the latest version is gdbm-1.9.x and that should work fine for prefix. your change won't work w/out bumping the EAPI. >- --includedir=/usr/include/gdbm \ >+ --includedir=$EPREFIX/usr/include/gdbm \ quoting is missing, and vars should braces around them however, this would probably be better: --includedir='$(prefix)/include/gdbm' >+ --oldincludedir=$EPREFIX/usr/include \ why do you need to set oldincludedir ? >+ mv "${D}"$EPREFIX/usr/include/gdbm/gdbm.h "${D}"$EPREFIX/usr/include/ || die no ... this is what $ED is for (In reply to Daa Jaa from comment #1) we don't care about old versions. for prefix work, you should *only* be looking at the very latest. please cc prefix@gentoo.org when you file EPREFIX related bugs. Thank you SpanKY for all your remarks. @SpanKY : "we don't care about old versions. for prefix work, you should *only* be looking at the very latest." Is there a difference between the normal portage tree and the EPREFIX portage tree ? Where can I find the latest version of the latter ? When the EPREFIX will be working, I will test the adaptation of my patch to gdbm-1.9 before submitting it here. (In reply to Daa Jaa from comment #4) > Thank you SpanKY for all your remarks. > > @SpanKY : "we don't care about old versions. for prefix work, you should > *only* be looking at the very latest." > > Is there a difference between the normal portage tree and the EPREFIX > portage tree ? Where can I find the latest version of the latter ? What tree are you using? Have you ever done "emerge --sync"? My Prefix installation have sys-libs/gdbm-1.10 @Benda Xu: "Have you ever done "emerge --sync"?" emerge --sync has been done by bootstrap-prefix.sh, but my patch addresses a bug of bootstrap-prefix.sh happening BEFORE that emerge --sync, with the portage tree hardcoded in bootstrap-prefix.sh. (In reply to Daa Jaa from comment #6) > @Benda Xu: "Have you ever done "emerge --sync"?" > > emerge --sync has been done by bootstrap-prefix.sh, but my patch addresses a > bug of bootstrap-prefix.sh happening BEFORE that emerge --sync, with the > portage tree hardcoded in bootstrap-prefix.sh. I speculate that bug is fixed. The portage snapshot used by bootstrap-prefix.sh is updated regularly. |