Hi Francois, On Sat, 19 Mar 2011 06:09:10 +0100 Francois Tigeot <ftigeot@wolfpond.org> wrote:
Well, all my builds of the last few month were run without it.
That is luck and you dont want to count on that. Anyone using a variable GNUCOPY in the old build system has every right to expect it to contain a GNU cp.
Neat. Is there a timeframe for that ?
As soon as you have migrated all modules to the new system. ;D
I'm runnning DragonFly and the behavior has clearly changed. Should I remove/change the test in configure.in ?
You could set GNUCOPY to empty (on BSD as on OSX) if there isnt one available. But then the old build system will set GNUCOPY to a non-GNU cp. Likely you will get breakers now on BSD from that and issues might pop up again now and then as long as the old build system is around. So if you do that change, you would be completely responsible for fixing those yourself. Anyone assuming GNUCOPY to contain a GNU cp is perfectly ok, so doing that even in the old build system is absolutely innocent IMHO. Dont complain to them. Honestly, I think the time spend on working around the awkwardness of the old build system is better spend on migrating to the new build system though. Best Regards, Bjoern -- https://launchpad.net/~bjoern-michaelsen
Attachment:
signature.asc
Description: PGP signature