From: Keith M. <kei...@us...> - 2007-10-30 00:38:08
|
In the thread "MSYS on Vista", on MinGW-users, I posted the comment: > Continuing the reorganisation, and rationalisation of the package > layout, I've moved some of the `Snapshot' entries to a new `Technology > Preview' release, within the `MSYS: Base System' package. I haven't > finished the move yet, so for the short term, you may need to look in > both places. I've actually moved all but six of the tarballs out of the `Snapshot' package: the `lpr' tarball into the `MSYS: Supplementary Tools' package, since I don't think it needs to be in the Base System; the rest into the `MSYS: Base System' package. The six I've left behind are all binaries, and lack source; could the respective developers please rectify that omission. Regards, Keith. |
From: Keith M. <kei...@us...> - 2007-11-07 14:45:33
|
On Tue, 2007-10-30 at 00:38 +0000, Keith Marshall wrote: > The six I've left behind are all binaries, and lack source; could the > respective developers please rectify that omission. Ping: Earnie, Cesar, The six packages in question are:-- bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 bzip2-1.0.3-MSYS-1.0.11-snapshot.tar.bz2 diffutils-2.8.7-MSYS-1.0.11-snapshot.tar.bz2 file-4.16-MSYS-1.0.11-snapshot.tar.bz2 findutils-4.3.0-MSYS-1.0.11-snapshot.tar.bz2 gawk-3.1.5-MSYS-1.0.11-snapshot.tar.bz2 None of these are accompanied by source tarballs. I think they should be; indeed for those which are GPL, that's pretty much mandatory. In CVS, I can find:-- bash-3.1 bzip2-1.0.3 diffutils-2.8.7 findutils-4.3 gawk-3.1.5 but conspicuous by its absence:-- file-4.16 So, questions:-- 1) Is the CVS state up to date with your respective source trees? 2) If not, could you please make it so? 3) If yes, would you like to upload the necessary source tarballs? 4) Or, would you like me to check out from CVS, make dist, and do so? 5) What should we do about file-4.16? Especially since... In the `Current Release: msysDTK-1.0.1' collection, I see Chuck's:-- file-4.16-MSYS.tar.bz2 file-4.16-MSYS-src.tar.bz2 which are actually *newer* than the snapshot in the MSYS-1.0.11 technology preview collection, so I'm tempted to just hide this file-4.16-MSYS-1.0.11-snapshot.tar.bz2 Regards, Keith. |
From: Keith M. <kei...@us...> - 2007-11-07 17:41:54
|
On Wed, 2007-11-07 at 14:45 +0000, Keith Marshall wrote: > The six packages in question are:-- > > bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 > bzip2-1.0.3-MSYS-1.0.11-snapshot.tar.bz2 > diffutils-2.8.7-MSYS-1.0.11-snapshot.tar.bz2 > file-4.16-MSYS-1.0.11-snapshot.tar.bz2 > findutils-4.3.0-MSYS-1.0.11-snapshot.tar.bz2 > gawk-3.1.5-MSYS-1.0.11-snapshot.tar.bz2 FTR, I've now moved all of these, except file-4.16, to the TP release collection in `MSYS Base System'. > In the `Current Release: msysDTK-1.0.1' collection, I see Chuck's:-- > > file-4.16-MSYS.tar.bz2 > file-4.16-MSYS-src.tar.bz2 > > which are actually *newer* than the snapshot in the MSYS-1.0.11 > technology preview collection, So, I've left these visible, as current releases, equally suitable for use with MSYS-1.0.11. > so I'm tempted to just hide this > > file-4.16-MSYS-1.0.11-snapshot.tar.bz2 and I've left this behind, in the old `Snapshot:MSYS' package:release, with the `hidden' attribute set. Regards, Keith. |
From: Cesar S. <ces...@gm...> - 2007-11-07 21:27:59
|
Previously, Keith Marshall wrote: > Continuing the reorganisation, and rationalisation of the package > layout, I've moved some of the `Snapshot' entries to a new `Technology > Preview' release, within the `MSYS: Base System' package. Thanks for doing this, it also looks very well organized. Keith Marshall wrote: > Keith Marshall wrote: > > The six I've left behind are all binaries, and lack source; could the > > respective developers please rectify that omission. > > Ping: Earnie, Cesar, Pong. Sorry for the delay. > > The six packages in question are:-- > > bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 > bzip2-1.0.3-MSYS-1.0.11-snapshot.tar.bz2 > diffutils-2.8.7-MSYS-1.0.11-snapshot.tar.bz2 > file-4.16-MSYS-1.0.11-snapshot.tar.bz2 > findutils-4.3.0-MSYS-1.0.11-snapshot.tar.bz2 > gawk-3.1.5-MSYS-1.0.11-snapshot.tar.bz2 > > None of these are accompanied by source tarballs. I think they should > be; indeed for those which are GPL, that's pretty much mandatory. > I agree. It is also more convenient than fetching from CVS. > In CVS, I can find:-- > > bash-3.1 > bzip2-1.0.3 > diffutils-2.8.7 > findutils-4.3 > gawk-3.1.5 > > but conspicuous by its absence:-- > > file-4.16 > > So, questions:-- > > 1) Is the CVS state up to date with your respective source trees? I have a bug fix for bash that is not in CVS yet. > 2) If not, could you please make it so? Sure. > 3) If yes, would you like to upload the necessary source tarballs? I'd rather recompile and upload both source and binary, just to make sure one corresponds to the other. > 4) Or, would you like me to check out from CVS, make dist, and do so? No need, but thanks for the offer. I think I'll also include the script I've been using to build each of them. > 5) What should we do about file-4.16? Especially since... > > In the `Current Release: msysDTK-1.0.1' collection, I see Chuck's:-- > > file-4.16-MSYS.tar.bz2 > file-4.16-MSYS-src.tar.bz2 > > which are actually *newer* than the snapshot in the MSYS-1.0.11 > technology preview collection, so I'm tempted to just hide this > > file-4.16-MSYS-1.0.11-snapshot.tar.bz2 > I agree, it's the right thing to do. Regards, Cesar |
From: Cesar S. <ces...@gm...> - 2007-12-02 18:45:02
|
Keith Marshall wrote: > On Tue, 2007-10-30 at 00:38 +0000, Keith Marshall wrote: > > The six I've left behind are all binaries, and lack source; could the > > respective developers please rectify that omission. > All done. I placed the original binaries in the hidden Snapshot: MSYS release, and created fresh ones. > The six packages in question are:-- > > bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 > bzip2-1.0.3-MSYS-1.0.11-snapshot.tar.bz2 These had minor bug fixes. > diffutils-2.8.7-MSYS-1.0.11-snapshot.tar.bz2 Rebuilt from CVS. No source changes. > file-4.16-MSYS-1.0.11-snapshot.tar.bz2 Hidden (it has a newer version in the current DTK). > findutils-4.3.0-MSYS-1.0.11-snapshot.tar.bz2 > gawk-3.1.5-MSYS-1.0.11-snapshot.tar.bz2 Rebuilt from CVS. No source changes. Regards, Cesar |
From: Keith M. <kei...@us...> - 2007-12-02 21:35:02
|
On Sunday 02 December 2007 18:45, Cesar Strauss wrote: > Keith Marshall wrote: > > On Tue, 2007-10-30 at 00:38 +0000, Keith Marshall wrote: > > > The six I've left behind are all binaries, and lack source; could > > > the respective developers please rectify that omission. > > All done. I placed the original binaries in the hidden Snapshot: MSYS > release, and created fresh ones. Thanks, Cesar. Keith. |
From: Chris S. <ir0...@gm...> - 2007-12-03 00:11:13
|
Hey All, > > All done. I placed the original binaries in the hidden Snapshot: MSYS > > release, and created fresh ones. I know this has been asked quite a bit on the list, but should a snapshot be upload that has all the components? I know there was talk of a combined MinGW/MSYS installer, is anyone actively working on that? Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org |
From: Earnie B. <ea...@us...> - 2007-12-03 12:17:38
|
Quoting Chris Sutcliffe <ir0...@gm...>: > Hey All, > >> > All done. I placed the original binaries in the hidden Snapshot: MSYS >> > release, and created fresh ones. > > I know this has been asked quite a bit on the list, but should a > snapshot be upload that has all the components? I know there was talk > of a combined MinGW/MSYS installer, is anyone actively working on > that? > Not that I'm aware of, are you offering? There is a CVS tag for version 6. Earnie |
From: Chris S. <ir0...@gm...> - 2007-12-03 13:30:48
|
> > I know this has been asked quite a bit on the list, but should a > > snapshot be upload that has all the components? I know there was talk > > of a combined MinGW/MSYS installer, is anyone actively working on > > that? > > Not that I'm aware of, are you offering? There is a CVS tag for version 6. Is it an evolution of the 5.1.3 NSIS based installer that is in CVS? Chris -- Chris Sutcliffe http://emergedesktop.org |
From: Cesar S. <ces...@gm...> - 2007-12-03 23:17:47
|
Chris Sutcliffe wrote: > > > I know this has been asked quite a bit on the list, but should a > > > snapshot be upload that has all the components? That is the plan. The individual components are good for incrementally updating to the preview version, and for getting tools that are excluded from the main release. However, the final release will only have some carefully chosen files, to be worthy of its "minimal" name. Before it happens, however, I have to fix a text corruption issue with my build of "less"... > > > I know there was talk > > > of a combined MinGW/MSYS installer, is anyone actively working on > > > that? > > > > Not that I'm aware of, are you offering? There is a CVS tag for version 6. > I plan to work on this as soon as I release the new msysCORE tarball. > Is it an evolution of the 5.1.3 NSIS based installer that is in CVS? It is a reasonable starting point, I think. I have never used NSIS before, but I have read the manual, and I can understand the MinGW installer source code, now. Here are the needed tasks, as I see it: Initial tasks: 1) Review the submitted installer-related patches in the SF tracker. 2) Review the outstanding bugs in the SF tracker. 3) Review the feature requests in the SF tracker. Usability improvements: 1) Create manifest files as each package is installed. This is needed to assure clean upgrades and removals. 2) Preserve and use an existing user-specified mingw.ini file, it helps whenever the official version becomes stale. 3) When updating, show again the maturity level page (current, old, preview), so it can be changed at will. 4) When updating, show the full package list, allowing the user to remove deselected packages as well. MSYS integration tasks: 1) Read the MSYS versions from a section on the mingw.ini file, or maybe from a new msys.ini file. 2) Create a MSYS install option, with its own install location chooser (and maybe its own maturity level chooser?) Future tasks: 1) Add a page to select and install selected components from the msysDTK. 2) Maintain several MinGW/MSYS trees, each with its own maturity level. As always, if anyone wishes to help, it will be much appreciated. Regards, Cesar |
From: Chris S. <ir0...@gm...> - 2007-12-04 00:48:48
|
> Here are the needed tasks, as I see it: > > Initial tasks: > 1) Review the submitted installer-related patches in the SF tracker. > 2) Review the outstanding bugs in the SF tracker. > 3) Review the feature requests in the SF tracker. > > Usability improvements: > 1) Create manifest files as each package is installed. This is needed > to assure clean upgrades and removals. > 2) Preserve and use an existing user-specified mingw.ini file, it > helps whenever the official version becomes stale. > 3) When updating, show again the maturity level page (current, old, > preview), so it can be changed at will. > 4) When updating, show the full package list, allowing the user to > remove deselected packages as well. > > MSYS integration tasks: > 1) Read the MSYS versions from a section on the mingw.ini file, or > maybe from a new msys.ini file. > 2) Create a MSYS install option, with its own install location chooser > (and maybe its own maturity level chooser?) > > Future tasks: > 1) Add a page to select and install selected components from the msysDTK. > 2) Maintain several MinGW/MSYS trees, each with its own maturity level. I think that sums things up pretty well. > As always, if anyone wishes to help, it will be much appreciated. I have some NSIS experience, not a lot, but some. I'd be more than happy to help though. I'll checkout what's in CVS for the installer and see if I can figure out how it works. Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org |
From: Chris J. <ch...@co...> - 2007-12-04 04:00:25
|
Cesar Strauss wrote: > > Usability improvements: > 1) Create manifest files as each package is installed. This is needed > to assure clean upgrades and removals. I have something in the RTEMS installer which may be useful. Check this file: http://www.rtems.org/cgi-bin/viewcvs.cgi/rtems/contrib/mingw/rtems-autotools.nsi?rev=1.3 Look for 'InstallFilesFromFile' and 'un.RemoveFilesFromFile'. I have a list of files already somewhere which is not the install point and they are copied to the install point. > 2) Preserve and use an existing user-specified mingw.ini file, it > helps whenever the official version becomes stale. > 3) When updating, show again the maturity level page (current, old, > preview), so it can be changed at will. > 4) When updating, show the full package list, allowing the user to > remove deselected packages as well. 5) Provide a way for any other installer to locate an installed MinGW and/or MSYS package. > > As always, if anyone wishes to help, it will be much appreciated. > If you have any NSIS question feel free to send them my way. I am no expert but happy to answer questions if I can. |
From: Earnie B. <ea...@us...> - 2007-12-04 00:34:33
|
Quoting Chris Sutcliffe <ir0...@gm...>: >> > I know this has been asked quite a bit on the list, but should a >> > snapshot be upload that has all the components? I know there was talk >> > of a combined MinGW/MSYS installer, is anyone actively working on >> > that? >> >> Not that I'm aware of, are you offering? There is a CVS tag for version 6. > > Is it an evolution of the 5.1.3 NSIS based installer that is in CVS? > Not much evolved but yes. Earnie |