From: Christian Weisgerber on 29 Mar 2010 11:23 We only have autoconf 2.13 and 2.62 in the tree. Upstream authors are increasingly moving towards and _requiring_ newer versions (2.63, 2.64, 2.65), and if you have to run autoconf, that is a problem. Are there any plans to provide a newer autoconf version? -- Christian "naddy" Weisgerber naddy(a)mips.inka.de _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Ion-Mihai Tetcu on 29 Mar 2010 11:26 On Mon, 29 Mar 2010 15:23:48 +0000 (UTC) naddy(a)mips.inka.de (Christian Weisgerber) wrote: > We only have autoconf 2.13 and 2.62 in the tree. Upstream authors > are increasingly moving towards and _requiring_ newer versions > (2.63, 2.64, 2.65), and if you have to run autoconf, that is a > problem. Are there any plans to provide a newer autoconf version? Yes, it's in work, but won't be ready before at least a month. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu(a)FreeBSD.org, PGP Key ID 057E9F8B493A297B
|
Pages: 1 Prev: Now OK (Re: cvs commit: ports/print/panda/files patch-images.c) Next: "stable" ports? |