Quote:
Originally Posted by dartefi
Maybe so, but what if I'm a developer and need to compile to check my changes? The issue is autoconf-2.63. The m4 files are completely different, they don't even have the same names.
|
If so one would argue that the easiest way to test your patches would be to submit them to the OBS and let it compile the patched version for you.
But if you really want autoconf 2.13... it is available in the mozilla repo.
Code:
$ webpin autoconf
20 results (5 packages) found for "autoconf" in openSUSE_111
* autoconf: A GNU Tool for Automatically Configuring Source Code
- 2.63 [suse-oss | windows:/mingw | Application:/Geo | home:/nadvornik:/my_packages | home:/fstrba:/CrossMingw:/test]
- 2.60 [Printing]
- 2.61 [home:/vitsoft:/asterisk-zaptel | home:/vitsoft]
* autoconf-el: Emacs mode for editing GNU Autoconf scripts
- 2.63 [suse-oss]
* autoconf213: A GNU Tool for Automatically Configuring Source Code
- 2.13 [Moblin:/UI | home:/hfiguiere | home:/dragonagat | mozilla | home:/maw | home:/anshuljain]
* cups-autoconfig: A Utility to Auto-configure Printers
- 0.1.0 [suse-oss]
* sane-backends-autoconfig: USB Scanner Autoconfiguration
- 1.0.19 [suse-oss | home:/DocB]
- 1.0.20 [home:/arakeis]