• R/O
  • HTTP
  • SSH
  • HTTPS

Commit

Tags
No Tags

Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

The MinGW.org Installation Manager Tool


Commit MetaInfo

Revisione491d7108117af53892e54dff80747194d4d0984 (tree)
Time2013-09-05 00:45:38
AuthorKeith Marshall <keithmarshall@user...>
CommiterKeith Marshall

Log Message

mingw-get-0.6.0-mingw32-beta-20130904-1 released.

Change Summary

Incremental Difference

--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
1+2013-09-04 Keith Marshall <keithmarshall@users.sourceforge.net>
2+
3+ mingw-get-0.6.0-mingw32-beta-20130904-1 released.
4+
5+ * srcdist-doc/NEWS.in srcdist-doc/README.in: Release notes updated.
6+ * srcdist-doc/INSTALL.in: Installation instructions updated.
7+ * All files (r0-6-0-beta-20130904-1): Tag assigned.
8+
19 2013-08-26 Keith Marshall <keithmarshall@users.sourceforge.net>
210
311 Implement retry throttling for failed internet connections.
--- a/srcdist-doc/INSTALL.in
+++ b/srcdist-doc/INSTALL.in
@@ -14,21 +14,92 @@ source code distribution tarball.
1414 Please report bugs as directed at http://mingw.org/Reporting_Bugs
1515
1616
17-First Time Installation of a Binary Release
18--------------------------------------------
17+First Time Installation of a Current Binary Release
18+---------------------------------------------------
19+
20+Note that, as of release 0.6.0, the installation procedure for mingw-get
21+has been significantly simplified. The installation instructions which
22+follow relate to this release, and later; for instructions relating to
23+any earlier release, or if you are unable to run the new setup tool on
24+any legacy version of Windows, please refer to the following section,
25+under the heading "First Time Installation of a Legacy Binary Release".
1926
2027 To install mingw-get, visit the MinGW files repository at:
2128
2229 http://sourceforge.net/projects/mingw/files
2330
24-and, from the "Automated&nbsp;MinGW&nbsp;Installer/mingw-get" folder,
31+then, from the "Installer" folder,
32+download and run mingw-get-setup.exe, and select your choices from the
33+options presented [*], to install mingw-get. When this has completed,
34+you will then be offered the option to immediately continue with the
35+installation of a basic selection of MinGW packages [**]. If you do
36+choose to continue with package selection, this will be processed by an
37+integrated preview of the mingw-get GUI application, (regardless of
38+whether you have accepted or declined the option to install the GUI); to
39+complete your initial installation:--
40+
41+- Select individual packages, within the upper right hand "list-view"
42+ pane of the GUI window;
43+
44+- From the "Package" menu, (which also appears as a pop-up, when you
45+ click the status icon at the left hand side of the list entry), select
46+ the option to "Mark for Installation", in respect of each package
47+ which you wish to install;
48+
49+- Having so marked all packages which you wish to install, from the
50+ "Installation" menu select the "Apply Changes" option, to complete
51+ your initial installation.
52+
53+After you have completed the installation of mingw-get, as described
54+above, and regardless of whether you chose to install additional
55+packages, or not, you are advised to review the configuration, as
56+specified in your profile.xml file, and noting in particular, any new
57+features which are described in the supplied defaults.xml file, if you
58+have a profile.xml from a previous release; please refer to the section
59+below, under the heading "Specifying the Configuration", for details.
60+
61+[*] By default, mingw-get-setup.exe will offer to install mingw-get into
62+the "C:\MinGW" directory. You are *strongly* recommended to adopt this
63+default; however, if you do decide to change it, please *do* choose an
64+alternative with no white space within its absolute path name.
65+In particular, those who choose to ignore
66+this advice, and install MinGW into some subdirectory of (for example)
67+C:\Program&nbsp;Files", usually discover to their cost that certain
68+tools may not work correctly.
69+
70+[**] The set of packages offered, as the foundation for a basic
71+installation, are equivalent to those offered by the mingw-get-inst.exe
72+companion to earlier releases of mingw-get. Unlike mingw-get-inst.exe,
73+mingw-get-setup.exe, does *not* insist that you install the basic GCC
74+compiler suite. You are free to install it, or not, at your own option;
75+if you do wish to install it, please select the "mingw32-base" package,
76+which is the equivalent of the minimum mandatory selection imposed by
77+mingw-get-inst.exe
78+
79+
80+First Time Installation of a Legacy Binary Release
81+--------------------------------------------------
82+
83+The instructions which follow relate to the installation of mingw-get
84+releases prior to version 0.6.0; they also apply in the case of later
85+versions, where a legacy version of Windows may not permit you to run
86+the new mingw-get-setup.exe tool. For installation of release 0.6.0, or
87+any later release, using the new tool, please refer to the preceeding
88+section, under the heading "First Time Installation of a Current Binary
89+Release".
90+
91+To install mingw-get, visit the MinGW files repository at:
92+
93+ http://sourceforge.net/projects/mingw/files
94+
95+and, from the "Installer/mingw-get-<version>-<class>-<release>" folder,
2596 download your choice of either:
2697
27- {PACKAGE_DISTNAME}-bin.zip
98+ mingw-get-<version>-mingw32-<class>-<release>-bin.zip
2899
29100 or (preferred, if you know how to unpack it):
30101
31- {PACKAGE_DISTNAME}-bin.tar.gz
102+ mingw-get-<version>-mingw32-<class>-<release>-bin.tar.xz
32103
33104 Whichever of these you choose to download, you should unpack it into
34105 the directory in which you intend to host your MinGW installation; (we
@@ -60,7 +131,7 @@ above warning, you do decide to adopt an alternative installation path,
60131 then please substitute your alternative prefix, as appropriate, where this
61132 document refers to C:\MinGW.
62133
63-[**] If you have chosen {PACKAGE_DISTNAME}-bin.tar.gz as your installation
134+[**] If you have chosen {PACKAGE_DISTNAME}-bin.tar.xz as your installation
64135 source, rather than {PACKAGE_DISTNAME}-bin.zip, you may like to create the
65136 directory:
66137
@@ -182,6 +253,15 @@ In order to build mingw-get from source, you will require:
182253 from libxz sources no older than version 4.999.9beta, with a snapshot
183254 release date of 2009-12-09 or later).
184255
256+- A statically linkable liblua.a for the native MS-Windows host,
257+ together with its associated header files; (this should be binary
258+ compatible with the lua-5.2.0 release, as offered by MinGW.org).
259+
260+- A statically linkable libwtklite.a, together with its associated
261+ header files; (this is a MinGW.org specific product, currently offered
262+ only in source format, which you are advised to build and install for
263+ yourself).
264+
185265 Having provisioned a suitable build platform, with these pre-requisite
186266 libraries installed, you should obtain and unpack the source tarball,
187267 {PACKAGE_DISTNAME}-src.tar.gz, in any working directory of your choice,
@@ -234,7 +314,7 @@ to create an installation tarball, which may be deployed simply by
234314 unpacking it in the /mingw root directory, on any host you choose.
235315
236316
237-Building and Installing from Source in CVS
317+Building and Installing from Source in Git
238318 ------------------------------------------
239319
240320 If, rather than building mingw-get from the source code provided in the
@@ -242,7 +322,8 @@ form of a release tarball, you prefer to keep on the cutting edge of
242322 development within the public CVS repository, there are a few additional
243323 pre-requisites which you must satisfy on your build platform:
244324
245-- You must have a CVS client, which you can use to fetch the source code
325+- You must have either a git client, or a mercurial client with the
326+ hggit extension enabled, which you can use to fetch the source code
246327 from the repository, and subsequently keep it current.
247328
248329 - You must have the GNU autoconf package, with a version number of 2.59
@@ -257,40 +338,49 @@ pre-requisites which you must satisfy on your build platform:
257338 Provided you can satisfy (at least the first three of) these additional
258339 pre-requisites, you may check out the latest source code thus [*]:
259340
260-! $ export CVSROOT
261-! $ CVSROOT=:pserver:anonymous@mingw.cvs.sf.net:/cvsroot/mingw
262-! $ cvs login
263-! $ cvs -z3 co -P mingw-get
341+! $ git clone git://git.code.sf.net/p/mingw/mingw-get
342+
343+or:
344+
345+! $ hg clone git://git.code.sf.net/p/mingw/mingw-get
264346
265347 This will create a working copy of the mingw-get source tree, in the
266-mingw-get subdirectory of your current working directory.
348+mingw-get subdirectory of your current working directory [**].
267349
268350 [*] If you are an accredited MinGW Developer, you may prefer to use the
269-:ext: access protocol of CVS, in conjunction with your registered SSH
270-keys, to access the CVS repository; in this case, you should know the
351+SSH access protocol for git, in conjunction with your registered SSH
352+keys, to access the git repository; in this case, you should know the
271353 appropriate procedure to use, in place of the above.
272354
273-Having thus obtained your working copy of the source code from the CVS
355+[**] Note that, if you are a git user, you *must* perform an additional
356+checkout step, (which is not necessary for hg users):
357+
358+! $ cd mingw-get
359+! $ git submodule add ../build-aux
360+
361+Having thus obtained your working copy of the source code from the git
274362 repository, you should then:
275363
276364 ! $ cd mingw-get
277365 ! $ autoconf
278366
279-to generate the configure script, and then:
367+(git users should omit the 'cd mingw-get' step, since they will already
368+be in the appropriate directory, following the addition of the build-aux
369+submodule), to generate the configure script, and then:
280370
281371 ! $ mkdir obj
282372 ! $ cd obj
283373 ! $ ../configure --prefix=/mingw [options ...]
284374 ! $ make
285375
286-to progress the build [**], as in the previous case of building from the
287-source code extracted from a distribution tarball.
376+to progress the build [***], as in the previous case of building from
377+the source code extracted from a distribution tarball.
288378
289-[**] Notice that here we choose to build in a subdirectory called obj;
290-when building from source in CVS, building in-source becomes even less
379+[***] Notice that here we choose to build in a subdirectory called obj;
380+when building from source in git, building in-source becomes even less
291381 desirable than it is when building from distributed source. The choice
292382 of obj for the build directory name is dictated by the configuration of
293-mingw-get's CVS module itself; cvs "knows" that this directory does not
294-contain any source files of interest to it.
383+mingw-get's git module itself; both git and hg "know" that this
384+directory does not contain any source files of interest to them.
295385
296386 $RCSfile$: end of file
--- a/srcdist-doc/NEWS.in
+++ b/srcdist-doc/NEWS.in
@@ -9,6 +9,56 @@ historical record is restricted to recent releases; the full history is
99 recorded in the NEWS file, which is included in the source code package.
1010
1111
12+mingw-get-0.6.0-mingw32-beta-20130904-1
13+---------------------------------------
14+
15+Release date: 2013-09-04
16+
17+This is the first release to incorporate a working prototype for the
18+mingw-get GUI client, together with the integrated mingw-get-setup.exe
19+tool. With the advent of these additional capabilities, the existing
20+mingw-get-inst.exe wrapper becomes redundant, and is now deprecated;
21+it will be withdrawn after the next mingw-get release.
22+
23+With this release of mingw-get-setup.exe, first time installation of
24+mingw-get has become considerably simpler than previously; please see
25+the "Installation Instructions" for further information.
26+
27+In addition to the addition of the GUI client, and the simplified first
28+time installation procedure, this release incorporates the following new
29+user visible features:--
30+
31+- New "preferences" section in profile.xml; this allows users to adjust
32+ the default behaviour for command line options such as "--start-menu"
33+ and "--desktop", to allow the automatic creation of shortcuts, (for
34+ packages which provide them), without requiring explicit specification
35+ of the option on every mingw-get invocation. See the comments within
36+ defaults.xml, for configuration instructions.
37+
38+- The output from "mingw-get --help" has been revised, to provide a
39+ better explanation of the use of the "version selection" feature,
40+ which allows users to force installation of a particular non-current
41+ version of any package.
42+
43+- The "gui.exe" subsidiary program has been renamed as "guistub.exe"; it
44+ remains in place, with this new name, to furnish diagnostics, in the
45+ event that the user attempts to invoke the GUI from the command line,
46+ when no GUI support has been installed. Such GUI support is now
47+ provided by "guimain.exe"; this may be installed optionally, by
48+ choosing to install the "mingw-get-gui" package.
49+
50+- Internal "globbing" of command line arguments is now explicitly
51+ disabled; (any benefit of ever having supported this seems dubious;
52+ however, external "globbing" by shells, such as MSYS' sh.exe and
53+ bash.exe is not, and cannot be, affected by this change).
54+
55+- For users wishing to follow development at the source code level, the
56+ master source code repository has been relocated from CVS, to a new
57+ git repository at git://git.code.sourceforge.net/p/mingw/mingw-get;
58+ please refer to the INSTALL file, in the current source distribution,
59+ for further information on accessing this repository.
60+
61+
1262 mingw-get-0.5-mingw32-beta-20120426-1
1363 -------------------------------------
1464
@@ -125,6 +175,15 @@ The following new features have been implemented:--
125175 as --start-menu=all-users, to make such shortcuts available in the
126176 start menus of all users.
127177
178+;--------8<-------------------- cut-line -------------------->8--------
179+;
180+; Any text added below the cut-line will be included in the README
181+; file, which is to be included in the source distribution, but it
182+; will be excluded from the readme.txt file, which is to be used to
183+; add descriptive content on the SourceForge download page.
184+;
185+; Any lines, such as these, which begin with a semicolon in their
186+; first column (not indented), will be excluded from both files.
128187
129188 mingw-get-0.4-mingw32-alpha-1
130189 -----------------------------
@@ -210,15 +269,6 @@ been implemented:--
210269 licence packages associated with all runtime dependencies identified
211270 for the packages named in the command.
212271
213-;--------8<-------------------- cut-line -------------------->8--------
214-;
215-; Any text added below the cut-line will be included in the README
216-; file, which is to be included in the source distribution, but it
217-; will be excluded from the readme.txt file, which is to be used to
218-; add descriptive content on the SourceForge download page.
219-;
220-; Any lines, such as these, which begin with a semicolon in their
221-; first column (not indented), will be excluded from both files.
222272
223273 mingw-get-0.3-mingw32-alpha-2.1
224274 -------------------------------
--- a/srcdist-doc/README.in
+++ b/srcdist-doc/README.in
@@ -8,9 +8,9 @@ Description
88
99 mingw-get is a tool to assist users in the management of MinGW and MSYS
1010 software installations. Configured via an online XML database, which is
11-managed by the project maintainers, it offers a command line driven user
12-interface facilitating selective download and installation of packages
13-provided by the project.
11+managed by the project maintainers, it offers a choice of graphical and
12+command line driven user interfaces facilitating selective download and
13+installation of packages provided by the project.
1414
1515 The XML database provides maintainers with a mechanism for the
1616 specification of inter-package dependencies; this permits configuration
@@ -18,8 +18,6 @@ of any package, such that the end user may elect to install just that
1818 specific package, leaving mingw-get to ensure that all dependencies will
1919 be automatically satisfied at installation time.
2020
21-A graphical user interface is planned as a future enhancement.
22-
2321
2422 Licensing Terms
2523 ---------------