Re: Msys-1.0 program updates (autoconf)
Erwin Waterlander <waterlan-qWit8jRvyhVmR6Xm/[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <[email protected]> |
Op 23-2-2013 20:54, Alexey Pavlov schreef: > This is links to my updates: > > Autoconf: > https://www.dropbox.com/s/97qfyslaxtnk2zd/autoconf-2.69-1-msys-1.0.17-bin.tar.lzma > https://www.dropbox.com/s/u91061ofhkesfhq/autoconf-2.69-1-msys-1.0.17-doc.tar.lzma > https://www.dropbox.com/s/z9s18l4bxd4c5nz/autoconf-2.69-1-msys-1.0.17-lic.tar.lzma > https://www.dropbox.com/s/3v1e0wgrkzs4wyo/autoconf-2.69-1-msys-1.0.17-src.tar.lzma > > Automake: > https://www.dropbox.com/s/zdwknqg4xw05zhw/automake-1.12.6-1-msys-1.0.18-bin.tar.lzma > https://www.dropbox.com/s/1m2qhzfwtiq91zo/automake-1.12.6-1-msys-1.0.18-doc.tar.lzma > https://www.dropbox.com/s/xq0besj4nxi80yx/automake-1.12.6-1-msys-1.0.18-lic.tar.lzma > https://www.dropbox.com/s/pqtsb6y5zm5c269/automake-1.12.6-1-msys-1.0.18-src.tar.lzma > > Libtool: > https://www.dropbox.com/s/tjprro3laj51arb/libltdl-2.4.2-1-msys-1.0.17-dev.tar.lzma > https://www.dropbox.com/s/3thmr29ouj4z20j/libltdl-2.4.2-1-msys-1.0.17-dll-7.tar.lzma > https://www.dropbox.com/s/nre2omfuoiptkh5/libtool-2.4.2-1-msys-1.0.17-bin.tar.lzma > https://www.dropbox.com/s/tvcbfotm6x0uy2k/libtool-2.4.2-1-msys-1.0.17-doc.tar.lzma > https://www.dropbox.com/s/pak6cc4xygwtxr0/libtool-2.4.2-1-msys-1.0.17-lic.tar.lzma > https://www.dropbox.com/s/o0tu2o4kh3o7zrz/libtool-2.4.2-1-msys-1.0.17-src.tar.lzma > > I didn't have time to port scripts to mgwport if it not because I spend all my free time to port recent Cygwin to new MSYS2. > > Hi Alexey, Thanks a lot. I have also limited time. Let's do them one by one. First autoconf. Autoconf is already using mgwport, so you don't need to work on that. I noticed you didn't update the msys README file, the README file that is put under MSYS-PATCHES. You did not update the patch files. They still succeeded, with an offset, but I always update the patch files to the latest source. I don't know if there is an official policy on this topic... What you can do is run until preparation: mgwport autoconf-2.69-1.msysport prep And then you can go into the autoconf-2.69-1/ directory and run diff on the origsrc/ and src/ directories to create new patch files. If you first update the README file then you have that covered too. I ran this diff command for m4: diff -r -c -N --exclude=*.orig origsrc src > ../m4.patch Because you have published autoconf-2.69-1 on the internet, and you are going to make changes, your next version has to be autoconf-2.69-2. Because you never know who downloaded the files already. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb