First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 79472
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Peter Simons <simons@cryp.to>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
autoconf-archive-20050125.ebuild autoconf-archive-20050125.ebuild text/plain Peter Simons 2005-01-25 07:42 0000 721 bytes Details
autoconf-archive-20050214.ebuild sys-devel/autoconf-archive-20050214.ebuild text/plain Peter Simons 2005-02-14 11:25 0000 731 bytes Details
autoconf-archive-20050418.ebuild sys-devel/autoconf-archive-20050418 ebuild text/plain Peter Simons 2005-04-18 09:42 0000 731 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 79472 depends on: Show dependency tree
Show dependency graph
Bug 79472 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-01-25 07:41 0000 
Build and install the GNU Autoconf Macro Archive.

The archive contains just text files; there is no build process. Hence, it should work nicely on all platforms Gentoo supports. Where I could test it, on x86, it did.

I'm not sure how to handle the different version number markup correctly, but I think the way I have is okay.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Peter Simons 2005-01-25 07:42:24 0000 ------- 
Created an attachment (id=49480) [edit]
autoconf-archive-20050125.ebuild

------- Comment #2 From SpanKY 2005-01-26 14:23:13 0000 ------- 
sys-devel/ac-archive-0.5.57 is already in portage

------- Comment #3 From Peter Simons 2005-01-26 14:47:29 0000 ------- 
Sorry, I probably should have said something. That is in fact a different macro
archive, and it works with aclocal(1) rather requiring its own custom tools
(acinclude) to include macros in configure scripts. The documentation is also
quite a bit better. I think it would be worthwile to have both archives in
Portage, so that the user can choose.

Anyway, that's the GNU Autoconf Macro Archive, not ac-archive.sf.net.

------- Comment #4 From Peter Simons 2005-02-14 11:25:22 0000 ------- 
Created an attachment (id=51227) [edit]
sys-devel/autoconf-archive-20050214.ebuild

New release.

------- Comment #5 From Peter Simons 2005-04-18 09:42:46 0000 ------- 
Created an attachment (id=56586) [edit]
sys-devel/autoconf-archive-20050418 ebuild

New release.

------- Comment #6 From SpanKY 2005-04-27 21:17:37 0000 ------- 
ok, i cleaned up the ebuild and added to portage

for future reference:
- shell code in global scope is bad (i.e. executing things like sed)
- use make install DESTDIR=$D instead of einstall

thanks for the ebuild !

------- Comment #7 From Peter Simons 2005-05-03 05:07:07 0000 ------- 
I was wondering: What's the problem with einstall? Why does the alias exist if
its use is discouraged? I thought that einstall would be preferred over calling
make manually, but apparently it isn't?

Anyhow, thanks for getting the ebuild into portage. I looked at the changes
you've made -- next time I'll know better. ;-) 

There is a new version of the autoconf macro archive available, by the way. All
you have to do to update is:

 # cd /usr/portage/sys-devel/autoconf-archive/
 # cp autoconf-archive-2005.04.18.ebuild autoconf-archive-2005.05.02.ebuild

------- Comment #8 From SpanKY 2005-05-03 05:34:08 0000 ------- 
when einstall was designed years ago, its usage was a lot more common because
packages based on older autotools (and thus did not support DESTDIR) was more
common as well
First Last Prev Next    No search results available      Search page      Enter new bug