From: Charles W. <cwi...@us...> - 2010-09-06 17:09:46
|
I've reformatted, corrected, tested, and published all of the (unpublished) xml manifests used by mingw-get. Once you have a basic mingw-get installation, you can now do: mingw-get update mingw-get install <package-spec> To get an idea of the possible package specs, do this: grep 'package name=' /mingw/var/lib/mingw-get/data/*xml Specifying one of those names or aliases will install ALL of the components for that package. For more fine-grained control, append the component type: e.g. mingw-get install gendef-bin will install only the -bin component of the mingw32-gendef package, ignoring the -doc and -lic components. Some items of interest: mingw-dtk 'meta' package ------------------------ This meta package contains the components necessary to create a relatively complete MSYS installation suitable for most MinGW developers' needs. It includes the msys-base system, as well as the autotools (autoconf, automake, libtool, gettext, and libiconv) configured for use in maintaining and building native win32 (MinGW) programs. It includes m4, perl, vim, patch, cvs, guile, mktemp, bison, flex, lndir, and other useful command line tools. It also includes networking clients for ssh, rsh, telnet, and ftp protocols. autotools 'meta' package ------------------------ If you don't want ALL the stuff in mingw-dtk, you can just install this one. It will install only the mingw32 versions of the autotools, and their immediate requirements. msys-dvlpr 'meta' package (very few people will want this) ------------------------- This meta package contains the components necessary to build MSYS-dependent applications and libraries, as well as the MSYS DLL itself. -- Chuck |
From: Charles W. <cwi...@us...> - 2010-09-06 17:13:36
|
On 9/6/2010 1:08 PM, Charles Wilson wrote: > I've reformatted, corrected, tested, and published all of the > (unpublished) xml manifests used by mingw-get. Well, maybe not ALL: mingw32-catgets mingw32-man are still missing. There may be a few others, but we're real close to 100%. -- Chuck |
From: Roger P. <rog...@gm...> - 2010-09-23 17:25:42
|
>> I've reformatted, corrected, tested, and published all of the >> (unpublished) xml manifests used by mingw-get. I did notice that the gdb package, if installed by itself, causes an error popup "missing libexpat1.dll" (or something like that). Thanks. -r |
From: Charles W. <cwi...@us...> - 2010-09-24 02:37:20
|
On 9/23/2010 1:25 PM, Roger Pack wrote: > I did notice that the gdb package, if installed by itself, causes an > error popup "missing libexpat1.dll" (or something like that). You're right. mingw32-gdb.xml is missing a <requires> libexpat-dll statement. I'll fix that next time I upload a new package. -- Chuck |
From: Martin M. <vi...@gm...> - 2010-09-06 21:33:18
|
On Mon, Sep 6, 2010 at 7:08 PM, Charles Wilson < cwi...@us...> wrote: > I've reformatted, corrected, tested, and published all of the > (unpublished) xml manifests used by mingw-get. > Great work, thanks!!! I really like the command line idea more than anything before. > Once you have a basic mingw-get installation, you can now do: > > mingw-get update > mingw-get install <package-spec> > > To get an idea of the possible package specs, do this: > > grep 'package name=' /mingw/var/lib/mingw-get/data/*xml > 'mingw-get list' or something like that maybe? |
From: Charles W. <cwi...@us...> - 2010-09-06 22:34:06
|
On 9/6/2010 5:33 PM, Martin Mocko wrote: > On Mon, Sep 6, 2010 at 7:08 PM, Charles Wilson: >> To get an idea of the possible package specs, do this: >> >> grep 'package name=' /mingw/var/lib/mingw-get/data/*xml >> > > 'mingw-get list' or something like that maybe? Nope, right now mingw-get doesn't have any query modes (or any option parsing at all). Patches Gratefully Considered. -- Chuck |
From: LRN <lr...@gm...> - 2010-09-07 04:27:25
|
On 06.09.2010 21:08, Charles Wilson wrote: > To get an idea of the possible package specs, do this: > > grep 'package name=' /mingw/var/lib/mingw-get/data/*xml > > Even better: grep 'package name=' /mingw/var/lib/mingw-get/data/*.xml | sed 's/.*<package name=\"\(.*\)\".*/\1/' |
From: Keith M. <kei...@us...> - 2010-09-22 02:24:22
|
On 07/09/2010, LRN <lr...@gm...> wrote: > On 06.09.2010 21:08, Charles Wilson wrote: >> To get an idea of the possible package specs, do this: >> >> grep 'package name=' /mingw/var/lib/mingw-get/data/*xml > > Even better: > > grep 'package name=' /mingw/var/lib/mingw-get/data/*.xml | sed > 's/.*<package name=\"\(.*\)\".*/\1/' And, even better still--since you've done the hard part of the sed expression--dispense with grep altogether: sed -n 's/.*<package name=\"\(.*\)\".*/\1/p' /mingw/var/lib/mingw-get/data/*.xml -- Regards, Keith |
From: Thomas S. <tks...@gm...> - 2010-09-22 14:56:11
|
Thanks Keith Works for me. But does not show some names that I have successfully installed, mingw32-libz-dev for example. I suppose those are aliases that this sed script does not pick up? -- Tom On Tue, Sep 21, 2010 at 10:00 PM, Keith Marshall < kei...@us...> wrote: > On 07/09/2010, LRN <lr...@gm...> wrote: > > On 06.09.2010 21:08, Charles Wilson wrote: > >> To get an idea of the possible package specs, do this: > >> > >> grep 'package name=' /mingw/var/lib/mingw-get/data/*xml > > > > Even better: > > > > grep 'package name=' /mingw/var/lib/mingw-get/data/*.xml | sed > > 's/.*<package name=\"\(.*\)\".*/\1/' > > And, even better still--since you've done the hard part of the sed > expression--dispense with grep altogether: > > sed -n 's/.*<package name=\"\(.*\)\".*/\1/p' > /mingw/var/lib/mingw-get/data/*.xml > > -- > Regards, > Keith > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list > etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: LRN <lr...@gm...> - 2010-09-22 15:35:47
|
On 22.09.2010 18:56, Thomas Sharpless wrote: > Thanks Keith > > Works for me. But does not show some names that I have successfully > installed, mingw32-libz-dev for example. I suppose those are aliases that > this sed script does not pick up? <package name="mingw32-zlib" alias="zlib"> ... <component class="doc"> ... <component class="lic"> ... <component class="man"> ... </package> <package name="mingw32-libz" alias="libz"> ... <component class="dll"> ... <component class="dev"> ... </package> Does that answer your question? > -- Tom > > On Tue, Sep 21, 2010 at 10:00 PM, Keith Marshall< > kei...@us...> wrote: > >> On 07/09/2010, LRN<lr...@gm...> wrote: >>> On 06.09.2010 21:08, Charles Wilson wrote: >>>> To get an idea of the possible package specs, do this: >>>> >>>> grep 'package name=' /mingw/var/lib/mingw-get/data/*xml >>> Even better: >>> >>> grep 'package name=' /mingw/var/lib/mingw-get/data/*.xml | sed >>> 's/.*<package name=\"\(.*\)\".*/\1/' >> And, even better still--since you've done the hard part of the sed >> expression--dispense with grep altogether: >> >> sed -n 's/.*<package name=\"\(.*\)\".*/\1/p' >> /mingw/var/lib/mingw-get/data/*.xml >> >> -- >> Regards, >> Keith |
From: Keith M. <kei...@us...> - 2010-09-23 01:31:12
|
On 22/09/2010, Thomas Sharpless <tks...@gm...> wrote: > Thanks Keith > > Works for me. But does not show some names that I have successfully > installed, mingw32-libz-dev for example. Does it not list mingw32-zlib? (Sorry, I only have web mail at present, and no way to try it for myself). > I suppose those are aliases that > this sed script does not pick up? The -dev suffix isn't part of the package name; it comes from the class attribute of the component element, *within* the package element. If you want that level of detail, then you'd need to modify the sed expression, or maybe better, use awk instead. BTW, *please* don't top post; it makes it so much harder to preserve context, and as you see, I've chucked the script to which you refer. -- Regards, Keith. |
From: Charles W. <cwi...@us...> - 2010-09-23 05:54:23
Attachments:
mingw-get-pkglist.awk
|
On 9/22/2010 9:31 PM, Keith Marshall wrote: > or maybe better, use awk instead. See attached. -- Chuck |
From: Thomas S. <tks...@gm...> - 2010-09-23 12:26:47
|
Chuck On Thu, Sep 23, 2010 at 1:52 AM, Charles Wilson < cwi...@us...> wrote: > On 9/22/2010 9:31 PM, Keith Marshall wrote: > > or maybe better, use awk instead. > > See attached. > > Spiffy. Should be very useful. Thanks a lot. -- Tom |
From: Keith M. <kei...@us...> - 2010-09-24 00:50:03
|
On 23/09/2010, Charles Wilson <cwi...@us...> wrote: > On 9/22/2010 9:31 PM, Keith Marshall wrote: >> or maybe better, use awk instead. > > See attached. Neat, Chuck. One suggestion; add a shebang: #! /bin/awk -f at line 1, and it becomes executable. -- Regards, Keith. |
From: Roger P. <rog...@gm...> - 2010-09-30 22:36:54
|
>> or maybe better, use awk instead. > > See attached. Maybe mingw-get could include "helper scripts" like this (in C:\MinGW\var\lib\mingw-get\data or what not). This could simplify things a bit. -r |
From: Keith M. <kei...@us...> - 2010-09-24 00:50:48
|
On 23/09/2010, Roger Pack <rog...@gm...> wrote: >>> I've reformatted, corrected, tested, and published all of the >>> (unpublished) xml manifests used by mingw-get. > > I did notice that the gdb package, if installed by itself, causes an > error popup "missing libexpat1.dll" (or something like that). Shouldn't do. I'm sure I added the dependency when I originally published the mingw32-gdb.xml manifest, and mingw-get install mingw32-gdb-bin definitely pulled in the requisite libexpat-dll for me, when I tested it, so it should still do so, unless the requirements spec has been subsequently deleted. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2010-10-05 19:00:44
|
On Friday 24 September 2010 01:50:39 Keith Marshall wrote: > On 23/09/2010, Roger Pack <rog...@gm...> wrote: > >>> I've reformatted, corrected, tested, and published all of the > >>> (unpublished) xml manifests used by mingw-get. > > > > I did notice that the gdb package, if installed by itself, causes > > an error popup "missing libexpat1.dll" (or something like that). > > Shouldn't do. I'm sure I added the dependency when I originally > published the mingw32-gdb.xml manifest, and > > mingw-get install mingw32-gdb-bin > > definitely pulled in the requisite libexpat-dll for me, when I tested > it, so it should still do so, unless the requirements spec has been > subsequently deleted. Darn. Mea culpa. Postmortem analysis obviously isn't going to help now, but just for the record, my sandbox copy of mingw32-gdb.xml has <!-- From GDB-7 onward, MinGW builds require libexpat-1.dll --> <requires eq="mingw32-libexpat-*-mingw32-dll-1.tar" /> added to the 1.1 version from CVS, (and published as issue 2010052101 for general download availability on SF), so the requirement *had* been addressed at that time. However, it seems that I neglected to commit that addition to CVS, so the requirement was overlooked on subsequent publication of an updated manifest. Sorry about that, and many thanks to Chuck for correcting the omission in my absence. -- Regards, Keith. |