Menu
▾
▴
mingw-users
|
From: Stefano S. <ste...@po...> - 2010-06-14 08:24:53
|
Hi all, I wonder if there is some way to automate the installation of all the packages of MSYS using e.g. through scripting (Python, Perl, whatever). I know there is the mingw-get develpment in progress, but I would like a viable solution *today* rather than in some week/month/year. The automated procedure would include the download of all the packages, their decompression (I don't know how to automatically decompress, currently I'm using 7-zip+winrar), and the extraction in a given dir, and eventually the setup of the environment (e.g. to bind MSYS to the current installation of MinGW). The list of packages may be written down by the user, but this requires to know in advance the association between the packages which are going to be installed and the corresponding sourceforge URLs, I currently have no hint about how to get it. Regards. |
|
From: LRN <lr...@gm...> - 2010-06-14 08:44:17
|
On 14.06.2010 12:24, Stefano Sabatini wrote: > Hi all, > > I wonder if there is some way to automate the installation of all the > packages of MSYS using e.g. through scripting (Python, Perl, > whatever). > > I know there is the mingw-get develpment in progress, but I would like > a viable solution *today* rather than in some week/month/year. > > The automated procedure would include the download of all the > packages, their decompression (I don't know how to automatically > decompress, currently I'm using 7-zip+winrar), and the extraction in a > given dir, and eventually the setup of the environment (e.g. to bind > MSYS to the current installation of MinGW). > > The list of packages may be written down by the user, but this > requires to know in advance the association between the packages which > are going to be installed and the corresponding sourceforge URLs, I > currently have no hint about how to get it. > > Regards. > grep this mailing list (and/or Google) for "setup-mingw" |
|
From: Stefano S. <ste...@po...> - 2010-06-14 09:28:59
|
On date Monday 2010-06-14 12:44:06 +0400, LRN wrote: > On 14.06.2010 12:24, Stefano Sabatini wrote: > > Hi all, > > > > I wonder if there is some way to automate the installation of all the > > packages of MSYS using e.g. through scripting (Python, Perl, > > whatever). > > > > I know there is the mingw-get develpment in progress, but I would like > > a viable solution *today* rather than in some week/month/year. > > > > The automated procedure would include the download of all the > > packages, their decompression (I don't know how to automatically > > decompress, currently I'm using 7-zip+winrar), and the extraction in a > > given dir, and eventually the setup of the environment (e.g. to bind > > MSYS to the current installation of MinGW). > > > > The list of packages may be written down by the user, but this > > requires to know in advance the association between the packages which > > are going to be installed and the corresponding sourceforge URLs, I > > currently have no hint about how to get it. > > > > Regards. > > > grep this mailing list (and/or Google) for "setup-mingw" I found this: http://thread.gmane.org/gmane.comp.gnu.mingw.user/30854 setup-mingw.bat page: http://crosswire.org/~jmarsden/setup-mingw.html It installed an outdated versions of MinGW/MSYS, apart from this worked smoothly. What about to add a link to the MinGWiki, or even better actively update / maintain it? Regards. |
|
From: Stefano S. <ste...@po...> - 2010-06-15 08:06:41
|
On date Monday 2010-06-14 11:28:18 +0200, Stefano Sabatini wrote: > On date Monday 2010-06-14 12:44:06 +0400, LRN wrote: > > On 14.06.2010 12:24, Stefano Sabatini wrote: > > > Hi all, > > > > > > I wonder if there is some way to automate the installation of all the > > > packages of MSYS using e.g. through scripting (Python, Perl, > > > whatever). > > > > > > I know there is the mingw-get develpment in progress, but I would like > > > a viable solution *today* rather than in some week/month/year. > > > > > > The automated procedure would include the download of all the > > > packages, their decompression (I don't know how to automatically > > > decompress, currently I'm using 7-zip+winrar), and the extraction in a > > > given dir, and eventually the setup of the environment (e.g. to bind > > > MSYS to the current installation of MinGW). > > > > > > The list of packages may be written down by the user, but this > > > requires to know in advance the association between the packages which > > > are going to be installed and the corresponding sourceforge URLs, I > > > currently have no hint about how to get it. > > > > > > Regards. > > > > > grep this mailing list (and/or Google) for "setup-mingw" > > I found this: > http://thread.gmane.org/gmane.comp.gnu.mingw.user/30854 > > setup-mingw.bat page: > http://crosswire.org/~jmarsden/setup-mingw.html > > It installed an outdated versions of MinGW/MSYS, apart from this > worked smoothly. What about to add a link to the MinGWiki, or even > better actively update / maintain it? I also found this: http://lrn.no-ip.info/gstreamer/setup-mingw/setup-mingw.py which looks more flexible (the list of files is specified in an external file rather than being hardcoded in the script file itself). I suggest to adopt one of the above methods as the "official" installation method, that should possibly cut off the pain currently involved with the manual installation. A list of files for each MinGW/MSYS version may be provided as a separate file, well maybe they should be two different files. The list(s) may contain the complete list of packages, a mechanism for allowing to comment out the non required packages may be easily added. Regards. |
|
From: Damon R. <dam...@lm...> - 2010-06-14 11:08:55
|
On 6/14/2010 4:24 AM, Stefano Sabatini wrote: > > I know there is the mingw-get develpment in progress, but I would like > a viable solution *today* rather than in some week/month/year. I would like to second that motion. I tried to install msys this weekend and that is when I learned about the current state of msys. After looking at the list of packages to install I lost interest for the moment. Damon Register |
|
From: Stefano S. <ste...@po...> - 2010-06-15 10:56:56
Attachments:
setup-mingw.py
setup-mingw-files.txt
|
On date Tuesday 2010-06-15 10:06:02 +0200, Stefano Sabatini wrote: > On date Monday 2010-06-14 11:28:18 +0200, Stefano Sabatini wrote: > > On date Monday 2010-06-14 12:44:06 +0400, LRN wrote: > > > On 14.06.2010 12:24, Stefano Sabatini wrote: > > > > Hi all, > > > > > > > > I wonder if there is some way to automate the installation of all the > > > > packages of MSYS using e.g. through scripting (Python, Perl, > > > > whatever). > > > > > > > > I know there is the mingw-get develpment in progress, but I would like > > > > a viable solution *today* rather than in some week/month/year. > > > > > > > > The automated procedure would include the download of all the > > > > packages, their decompression (I don't know how to automatically > > > > decompress, currently I'm using 7-zip+winrar), and the extraction in a > > > > given dir, and eventually the setup of the environment (e.g. to bind > > > > MSYS to the current installation of MinGW). > > > > > > > > The list of packages may be written down by the user, but this > > > > requires to know in advance the association between the packages which > > > > are going to be installed and the corresponding sourceforge URLs, I > > > > currently have no hint about how to get it. > > > > > > > > Regards. > > > > > > > grep this mailing list (and/or Google) for "setup-mingw" > > > > I found this: > > http://thread.gmane.org/gmane.comp.gnu.mingw.user/30854 > > > > setup-mingw.bat page: > > http://crosswire.org/~jmarsden/setup-mingw.html > > > > It installed an outdated versions of MinGW/MSYS, apart from this > > worked smoothly. What about to add a link to the MinGWiki, or even > > better actively update / maintain it? > > I also found this: > http://lrn.no-ip.info/gstreamer/setup-mingw/setup-mingw.py > > which looks more flexible (the list of files is specified in an > external file rather than being hardcoded in the script file itself). > > I suggest to adopt one of the above methods as the "official" > installation method, that should possibly cut off the pain currently > involved with the manual installation. > > A list of files for each MinGW/MSYS version may be provided as a > separate file, well maybe they should be two different files. The > list(s) may contain the complete list of packages, a mechanism for > allowing to comment out the non required packages may be easily added. I slightly modified the script (added support for #-escaped lines and do not download files already present), the list of files in attachment is an adaptation of that compiled by Lars Uffman: http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT I'd like to see both the script and the list mentioned in the wiki. Regards. |
|
From: Lars U. <lar...@dl...> - 2010-06-15 11:18:32
|
Stefano Sabatini wrote: > I slightly modified the script (added support for #-escaped lines and > do not download files already present), the list of files in > attachment is an adaptation of that compiled by Lars Uffman: > http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT > > I'd like to see both the script and the list mentioned in the wiki. So would I - however, I just found that the wxWiki currently does not allow upload of text or py files - I will talk to the admins and see if this can be modified... However, since I am not familiar with python scripts - what's the advantage over a shell script? Apart from python being more powerful, of course... Best Regards, Lars -- Dipl.-Ing. Lars Uffmann Microgravity User Support Center (MUSC) Deutsches Zentrum für Luft- und Raumfahrt e.V. Linder Höhe D-51147 Köln phone: +49 (0)2203 601 2171 http://www.dlr.de/musc |
|
From: Lars U. <lar...@dl...> - 2010-06-16 07:47:06
|
Stefano Sabatini wrote: > I'm not familiar with batch windows script (I'm a unix guy), and for I wasn't talking about BATCH files! Beware! :D I am talking about *shell scripts* - such as ./configure and the likes... > the little I know of it I know it's very limited and quirky. The only > problem with python is that you need to install it, which required to > me less than 10 minutes so that shouldn't be an issue anyway. That's the thing - installing python - to be platform independant (in the sense of: avoid using a process that behaves differently on XP, Vista, Win7, wine, ReactOS and so on), under MSYS/MinGW this would require to build it from source. But we do want to use it to get & perform these installations in the first place. That's a hen/egg problem there... And - on second thought - this also applies to the shell scripts... So I guess even though I didn't mean it in the first place, I guess the windows/batch file that you mentioned would actually be the best solution... I may try and create something for that... If no one else does... Otherwise Python is indeed probably the better solution, even though python installation/usage may differ on different systems. There is, after all, the manual process... Best Regards, Lars -- Dipl.-Ing. Lars Uffmann Microgravity User Support Center (MUSC) Deutsches Zentrum für Luft- und Raumfahrt e.V. Linder Höhe D-51147 Köln phone: +49 (0)2203 601 2171 http://www.dlr.de/musc |
|
From: LRN <lr...@gm...> - 2010-06-16 08:07:00
|
On 16.06.2010 11:48, Lars Uffmann wrote: > Stefano Sabatini wrote: > >> I'm not familiar with batch windows script (I'm a unix guy), and for >> > I wasn't talking about BATCH files! Beware! :D > > I am talking about *shell scripts* - such as ./configure and the likes... > > >> the little I know of it I know it's very limited and quirky. The only >> problem with python is that you need to install it, which required to >> me less than 10 minutes so that shouldn't be an issue anyway. >> > That's the thing - installing python - to be platform independant (in > the sense of: avoid using a process that behaves differently on XP, > Vista, Win7, wine, ReactOS and so on), under MSYS/MinGW this would > require to build it from source. But we do want to use it to get & > perform these installations in the first place. That's a hen/egg problem > there... > > And - on second thought - this also applies to the shell scripts... So I > guess even though I didn't mean it in the first place, I guess the > windows/batch file that you mentioned would actually be the best solution... > > The best solution is a vbs script, because vbs interpreter is shipped with Windows since XP or so. It might not be as powerful as Python, but it beats the snot out of batch files. I just didn't care enough about the requirement of not installing extra interpreters at the time. |
|
From: Stefano S. <ste...@po...> - 2010-06-16 09:40:42
Attachments:
setup-mingw.py
setup-mingw.conf.py
|
On date Tuesday 2010-06-15 12:56:14 +0200, Stefano Sabatini wrote: > On date Tuesday 2010-06-15 10:06:02 +0200, Stefano Sabatini wrote: > > On date Monday 2010-06-14 11:28:18 +0200, Stefano Sabatini wrote: > > > On date Monday 2010-06-14 12:44:06 +0400, LRN wrote: > > > > On 14.06.2010 12:24, Stefano Sabatini wrote: > > > > > Hi all, > > > > > > > > > > I wonder if there is some way to automate the installation of all the > > > > > packages of MSYS using e.g. through scripting (Python, Perl, > > > > > whatever). > > > > > > > > > > I know there is the mingw-get develpment in progress, but I would like > > > > > a viable solution *today* rather than in some week/month/year. > > > > > > > > > > The automated procedure would include the download of all the > > > > > packages, their decompression (I don't know how to automatically > > > > > decompress, currently I'm using 7-zip+winrar), and the extraction in a > > > > > given dir, and eventually the setup of the environment (e.g. to bind > > > > > MSYS to the current installation of MinGW). > > > > > > > > > > The list of packages may be written down by the user, but this > > > > > requires to know in advance the association between the packages which > > > > > are going to be installed and the corresponding sourceforge URLs, I > > > > > currently have no hint about how to get it. > > > > > > > > > > Regards. > > > > > > > > > grep this mailing list (and/or Google) for "setup-mingw" > > > > > > I found this: > > > http://thread.gmane.org/gmane.comp.gnu.mingw.user/30854 > > > > > > setup-mingw.bat page: > > > http://crosswire.org/~jmarsden/setup-mingw.html > > > > > > It installed an outdated versions of MinGW/MSYS, apart from this > > > worked smoothly. What about to add a link to the MinGWiki, or even > > > better actively update / maintain it? > > > > I also found this: > > http://lrn.no-ip.info/gstreamer/setup-mingw/setup-mingw.py > > > > which looks more flexible (the list of files is specified in an > > external file rather than being hardcoded in the script file itself). > > > > I suggest to adopt one of the above methods as the "official" > > installation method, that should possibly cut off the pain currently > > involved with the manual installation. > > > > A list of files for each MinGW/MSYS version may be provided as a > > separate file, well maybe they should be two different files. The > > list(s) may contain the complete list of packages, a mechanism for > > allowing to comment out the non required packages may be easily added. > > I slightly modified the script (added support for #-escaped lines and > do not download files already present), the list of files in > attachment is an adaptation of that compiled by Lars Uffman: > http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT > > I'd like to see both the script and the list mentioned in the wiki. I improved the script a bit, I put all the configuration in setup-ming.conf.py, this allows to clearly separate configuration from logic, which also allowed to simplify the script as the list of files doesn't need to be parsed anymore. I know that this is not recommended/sanctioned install method, but while mingw-get is in alpha this provides a viable way for a painless install. Regards. |
|
From: LRN <lr...@gm...> - 2010-06-16 10:46:54
|
On 16.06.2010 13:39, Stefano Sabatini wrote: > On date Tuesday 2010-06-15 12:56:14 +0200, Stefano Sabatini wrote: > >> On date Tuesday 2010-06-15 10:06:02 +0200, Stefano Sabatini wrote: >> >>> On date Monday 2010-06-14 11:28:18 +0200, Stefano Sabatini wrote: >>> >>>> On date Monday 2010-06-14 12:44:06 +0400, LRN wrote: >>>> >>>>> On 14.06.2010 12:24, Stefano Sabatini wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I wonder if there is some way to automate the installation of all the >>>>>> packages of MSYS using e.g. through scripting (Python, Perl, >>>>>> whatever). >>>>>> >>>>>> I know there is the mingw-get develpment in progress, but I would like >>>>>> a viable solution *today* rather than in some week/month/year. >>>>>> >>>>>> The automated procedure would include the download of all the >>>>>> packages, their decompression (I don't know how to automatically >>>>>> decompress, currently I'm using 7-zip+winrar), and the extraction in a >>>>>> given dir, and eventually the setup of the environment (e.g. to bind >>>>>> MSYS to the current installation of MinGW). >>>>>> >>>>>> The list of packages may be written down by the user, but this >>>>>> requires to know in advance the association between the packages which >>>>>> are going to be installed and the corresponding sourceforge URLs, I >>>>>> currently have no hint about how to get it. >>>>>> >>>>>> Regards. >>>>>> >>>>>> >>>>> grep this mailing list (and/or Google) for "setup-mingw" >>>>> >>>> I found this: >>>> http://thread.gmane.org/gmane.comp.gnu.mingw.user/30854 >>>> >>>> setup-mingw.bat page: >>>> http://crosswire.org/~jmarsden/setup-mingw.html >>>> >>>> It installed an outdated versions of MinGW/MSYS, apart from this >>>> worked smoothly. What about to add a link to the MinGWiki, or even >>>> better actively update / maintain it? >>>> >>> I also found this: >>> http://lrn.no-ip.info/gstreamer/setup-mingw/setup-mingw.py >>> >>> which looks more flexible (the list of files is specified in an >>> external file rather than being hardcoded in the script file itself). >>> >>> I suggest to adopt one of the above methods as the "official" >>> installation method, that should possibly cut off the pain currently >>> involved with the manual installation. >>> >>> A list of files for each MinGW/MSYS version may be provided as a >>> separate file, well maybe they should be two different files. The >>> list(s) may contain the complete list of packages, a mechanism for >>> allowing to comment out the non required packages may be easily added. >>> >> I slightly modified the script (added support for #-escaped lines and >> do not download files already present), the list of files in >> attachment is an adaptation of that compiled by Lars Uffman: >> http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT >> >> I'd like to see both the script and the list mentioned in the wiki. >> > I improved the script a bit, I put all the configuration in > setup-ming.conf.py, this allows to clearly separate configuration from > logic, which also allowed to simplify the script as the list of files > doesn't need to be parsed anymore. > > I know that this is not recommended/sanctioned install method, but > while mingw-get is in alpha this provides a viable way for a painless > install. > > Regards. > > I think it would have been better to have a single multi-line string (surrounded by triple double-quotes) which is later parsed into a list of strings by string.split () or by re.split (). This way you won't have to quote every file name (although that also makes comments impossible without resorting again to regular expressions to weed them out; although you can use a """ + \\n#comment\n""" construction to insert comments in the middle of multi-line strings, i think). |
|
From: Keith M. <kei...@us...> - 2010-06-16 20:13:37
|
On Wednesday 16 June 2010 10:39:58 Stefano Sabatini wrote: > I know that this is not recommended/sanctioned install method, but > while mingw-get is in alpha this provides a viable way for a > painless install. Just because mingw-get is designated "alpha", it doesn't mean that it isn't useable; in fact it is already *more* capable than the old NSIS based MinGW-5.1.x installers it is designated to replace. IOW, it is already a *completely* viable installation tool. Rather than mess about with developing your own home brewed scripts, which will *never* be sanctioned here, why not check out the prototype XML scripts from our mingw-dist CVS repository, and help us with the validation effort, so that mingw-get *will* meet your requirements? -- Regards, Keith. |
|
From: Stefano S. <ste...@po...> - 2010-06-17 07:09:20
|
On date Wednesday 2010-06-16 21:13:12 +0100, Keith Marshall wrote: > On Wednesday 16 June 2010 10:39:58 Stefano Sabatini wrote: > > I know that this is not recommended/sanctioned install method, but > > while mingw-get is in alpha this provides a viable way for a > > painless install. > > Just because mingw-get is designated "alpha", it doesn't mean that it > isn't useable; in fact it is already *more* capable than the old NSIS > based MinGW-5.1.x installers it is designated to replace. IOW, it is > already a *completely* viable installation tool. > > Rather than mess about with developing your own home brewed scripts, > which will *never* be sanctioned here, why not check out the prototype > XML scripts from our mingw-dist CVS repository, and help us with the > validation effort, so that mingw-get *will* meet your requirements? That's completely OK. Anyway, in order to avoid other people waste their time exerciting their scripting skills, I suggest to update the wiki, mention that mingw-get is already usable and possible add information about how to get it and use it. Regards. |
|
From: Stefano S. <ste...@po...> - 2010-06-15 12:38:32
|
On date Tuesday 2010-06-15 13:19:38 +0200, Lars Uffmann wrote: > Stefano Sabatini wrote: > > I slightly modified the script (added support for #-escaped lines and > > do not download files already present), the list of files in > > attachment is an adaptation of that compiled by Lars Uffman: > > http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT > > > > I'd like to see both the script and the list mentioned in the wiki. > > So would I - however, I just found that the wxWiki currently does not > allow upload of text or py files - I will talk to the admins and see if > this can be modified... > > However, since I am not familiar with python scripts - what's the > advantage over a shell script? Apart from python being more powerful, of > course... I'm not familiar with batch windows script (I'm a unix guy), and for the little I know of it I know it's very limited and quirky. The only problem with python is that you need to install it, which required to me less than 10 minutes so that shouldn't be an issue anyway. Regards. |
|
From: Earnie <ea...@us...> - 2010-06-15 17:00:50
|
Lars Uffmann wrote: > Stefano Sabatini wrote: >> I slightly modified the script (added support for #-escaped lines and >> do not download files already present), the list of files in >> attachment is an adaptation of that compiled by Lars Uffman: >> http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT >> >> I'd like to see both the script and the list mentioned in the wiki. > > So would I - however, I just found that the wxWiki currently does not > allow upload of text or py files - I will talk to the admins and see if > this can be modified... > > However, since I am not familiar with python scripts - what's the > advantage over a shell script? Apart from python being more powerful, of > course... > Why go to the trouble. Do not advertise it here. All alternative methods of delivering MinGW other than mingw-get or manual download are not sanctioned and are OFF-TOPIC for this list. Please give mingw-get a try. There are methods, already discussed and in the archives of this list for delivering MSYS and MinGW packages in automated fashion. Help with coding the rest would be helpful as well. Testing with feedback would be beneficial as well. -- Earnie -- http://www.for-my-kids.com |
|
From: Luis L. <lui...@gm...> - 2010-06-16 00:33:37
|
On Tue, Jun 15, 2010 at 1:00 PM, Earnie <ea...@us...> wrote: > Lars Uffmann wrote: >> Stefano Sabatini wrote: >>> I slightly modified the script (added support for #-escaped lines and >>> do not download files already present), the list of files in >>> attachment is an adaptation of that compiled by Lars Uffman: >>> http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT >>> >>> I'd like to see both the script and the list mentioned in the wiki. >> >> So would I - however, I just found that the wxWiki currently does not >> allow upload of text or py files - I will talk to the admins and see if >> this can be modified... >> >> However, since I am not familiar with python scripts - what's the >> advantage over a shell script? Apart from python being more powerful, of >> course... >> > > Why go to the trouble. Do not advertise it here. All alternative > methods of delivering MinGW other than mingw-get or manual download are > not sanctioned and are OFF-TOPIC for this list. > Apologizes for saying, but your non-advertisement statements are pretty negative to the project image. I respect you, and the work you do, but condoning in a continuous way every-single-post of people that is trying to figure out which component is needed to get them working is absurd. Nobody is endorsing it, or they will bring you with troubles when it doesn't work. First you need to understand the pieces and get you started for a contribution to show up. You stop them right there. > Please give mingw-get a try. There are methods, already discussed and > in the archives of this list for delivering MSYS and MinGW packages in > automated fashion. Help with coding the rest would be helpful as well. > Testing with feedback would be beneficial as well. > I've looked at mignw-get and that was the reason I posted the "manually installing MSYS packages" thread, which didn't get your attention. I wanted to contribute the required building recipes, but is not clear how the dependency chain machinery work, since there are 1.0.14 and 1.0.13 packages out there, and strange "runtime requirements" indicated that couldn't find some of them. Please, be positive. As you do, I also maintain several OSS and I know that interacting with people that do not research first is tiring. But you're treating everybody in the same way, without actually knowing what is their background. Forster experimentation, do not pushing it. Apologizes everybody for the complete off topic which might follow a ban of this list. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry |
|
From: Stefano S. <ste...@po...> - 2010-06-16 07:58:31
|
On date Tuesday 2010-06-15 13:00:38 -0400, Earnie wrote: > Lars Uffmann wrote: > > Stefano Sabatini wrote: > >> I slightly modified the script (added support for #-escaped lines and > >> do not download files already present), the list of files in > >> attachment is an adaptation of that compiled by Lars Uffman: > >> http://wiki.wxwidgets.org/HowTo:_Install_MSYS_and_MinGW_for_use_with_Eclipse_CDT > >> > >> I'd like to see both the script and the list mentioned in the wiki. > > > > So would I - however, I just found that the wxWiki currently does not > > allow upload of text or py files - I will talk to the admins and see if > > this can be modified... > > > > However, since I am not familiar with python scripts - what's the > > advantage over a shell script? Apart from python being more powerful, of > > course... > > > > Why go to the trouble. Do not advertise it here. All alternative > methods of delivering MinGW other than mingw-get or manual download are > not sanctioned and are OFF-TOPIC for this list. > > Please give mingw-get a try. There are methods, already discussed and > in the archives of this list for delivering MSYS and MinGW packages in > automated fashion. Help with coding the rest would be helpful as well. > Testing with feedback would be beneficial as well. Hi Ernie, I'll give mingw-get a try for sure and will report back, from what I read in the archive I couldn't even understand if that was already usable, and I needed a way to install it without to go through the hoops of a manual install, which *is* the install method for MSYS advertised by the wiki: http://www.mingw.org/wiki/MSYS |Installing MSYS |Up to MSYS 1.0.11, all components of MSYS were distributed in one |single installer you downloaded and ran. While convenient, this made |it difficult to update individual components. So, all the MSYS |components are now available as separate downloads. | |Currently, the best way to download MSYS is to choose the MSYS |components you want from the download page and to extract them one by |one in an empty directory. The MinGW devel|opers are working on a new |package manager to make this process automated. I tried it one time, felt the pain, failed to get it working, and didn't want to do it a second time ;-). Anyway this is the mingw user list so even discussing non-sanctioned installation methods, if they help to get your day done, is helpful and shouldn't be considered OT. Regards. |
|
From: Jasper H. <jas...@gm...> - 2010-06-16 10:47:10
|
arnie wrote: > Why go to the trouble. Do not advertise it here. All alternative > methods of delivering MinGW other than mingw-get or manual download are > not sanctioned and are OFF-TOPIC for this list. I would like to see this discussion not as advertising, but as a cry for help. A request to adopt a (semi-)official script to bridge the gap between the original automated installers and mingw-get. I do think you are actually losing users over the gap. It doesn't have to be anything fancy (that's what mingw is for) just s very simple script written in an hour or so. Only when the post turned up nothing useful, old script were dug up and people told about the modifications they had made to them. > Please give mingw-get a try. There are methods, already discussed and > in the archives of this list for delivering MSYS and MinGW packages in > automated fashion. Help with coding the rest would be helpful as well. > Testing with feedback would be beneficial as well. It might be because I did something wrong, but the last time I tried mingw-get it could only get me a copy of MinGW based on gcc 3 and that was the current alpha 2 release, if I am not mistaken. If this is just a property of the script (if it wasn't me doing something wrong) then it doesn't make it a very attractive option - in many cases it even completely rules it out. Jasper Horn |
|
From: Keith M. <kei...@us...> - 2010-06-16 20:43:24
|
On Wednesday 16 June 2010 11:40:28 Jasper Horn wrote: > > Please give mingw-get a try. There are methods, already > > discussed and in the archives of this list for delivering MSYS > > and MinGW packages in automated fashion. Help with coding the > > rest would be helpful as well. Testing with feedback would be > > beneficial as well. > > It might be because I did something wrong, but the last time I > tried mingw-get it could only get me a copy of MinGW based on gcc 3 > and that was the current alpha 2 release, if I am not mistaken. If > this is just a property of the script (if it wasn't me doing > something wrong) then it doesn't make it a very attractive option - > in many cases it even completely rules it out. I've made this point before; no doubt this will not be the last time I reiterate it: mingw-get is *not* in any way restricted to delivering only GCC-3.4.5. In fact, if you had been paying attention when the issue of GDB installation was raised a couple of weeks ago, (and IIRC it was by you, Jasper), I added it for you within 24 hours, *without* requiring you to do anything more than: $ mingw-get update $ mingw-get install gdb to install it, using the *unmodified* mingw-get alpha-2, which was already available to you, at the time. As I've pointed out in another reply in this same thread, our CVS repository includes a mingw-dist module, which already contains most, if not all of the XML manifests to enable mingw-get to deliver a comprehensive MSYS installation; they require validation, to ensure that they are error free and homogeneous, before we publish them. Currently, I am working through the validation exercise for the XML manifests for GCC-4.5 delivery; I will publish them as soon as I am satisfied as to their integrity. I haven't yet gotten around to even looking at the MSYS manifests; *you* can help with the validation process, and so accelerate progress toward publication, or you can continue to sit back and wait for someone else to do it all, and so compound the delay. -- Regards, Keith. |
|
From: Jasper H. <jas...@gm...> - 2010-06-16 22:31:51
|
Keith wrote: > In fact, if you had been paying attention when the > issue of GDB installation was raised a couple of weeks ago, (and IIRC > it was by you, Jasper), I did not raise that point. When someone else asked what the easiest way was, I told how I did it, and if it wasn't going to cause any problems. The response was that it wasn't going to cause any problems, so at the time I didn't try to install it through mingw-get, I had a working install after all. >I added it for you within 24 hours, *without* > requiring you to do anything more than: > > $ mingw-get update > $ mingw-get install gdb You are absolutely right, I must have missed mingw-get update when I tried mingw-get. However, I didn't put too much effort into it, that's why I started off my comment with the statement that it could well have been my own mistake rather than something related to mingw-get. As it happened, I had been trying a lot of things in order to see if I could get rid of the mingw10.dll dependency. After I failed at installing MinGW manually, I gave mingw-get a single try and then gave up. I'm sorry for not doing better research before bringing it up on the mailing list. Anyway, as I see how smooth this works, there might indeed be no gap to bridge. I'm sorry for the misinformed post I made earlier. Jasper Horn |
|
From: Stefano S. <ste...@po...> - 2010-06-17 14:03:23
|
On date Wednesday 2010-06-16 21:43:15 +0100, Keith Marshall wrote: > On Wednesday 16 June 2010 11:40:28 Jasper Horn wrote: > > > Please give mingw-get a try. There are methods, already > > > discussed and in the archives of this list for delivering MSYS > > > and MinGW packages in automated fashion. Help with coding the > > > rest would be helpful as well. Testing with feedback would be > > > beneficial as well. > > > > It might be because I did something wrong, but the last time I > > tried mingw-get it could only get me a copy of MinGW based on gcc 3 > > and that was the current alpha 2 release, if I am not mistaken. If > > this is just a property of the script (if it wasn't me doing > > something wrong) then it doesn't make it a very attractive option - > > in many cases it even completely rules it out. > > I've made this point before; no doubt this will not be the last time I > reiterate it: mingw-get is *not* in any way restricted to delivering > only GCC-3.4.5. In fact, if you had been paying attention when the > issue of GDB installation was raised a couple of weeks ago, (and IIRC > it was by you, Jasper), I added it for you within 24 hours, *without* > requiring you to do anything more than: > > $ mingw-get update > $ mingw-get install gdb > > to install it, using the *unmodified* mingw-get alpha-2, which was > already available to you, at the time. > > As I've pointed out in another reply in this same thread, our CVS > repository includes a mingw-dist module, which already contains most, > if not all of the XML manifests to enable mingw-get to deliver a > comprehensive MSYS installation; they require validation, to ensure > that they are error free and homogeneous, before we publish them. > Currently, I am working through the validation exercise for the XML > manifests for GCC-4.5 delivery; I will publish them as soon as I am > satisfied as to their integrity. I haven't yet gotten around to even > looking at the MSYS manifests; *you* can help with the validation > process, and so accelerate progress toward publication, or you can > continue to sit back and wait for someone else to do it all, and so > compound the delay. Hi Keith, I read this document: http://mingw.cvs.sourceforge.net/viewvc/mingw/mingw-get/README?view=markup then gave mingw-get a try: C:\MinGW\bin>mingw-get -version mingw-get version 0.1-alpha-2 Copyright (C) 2009, 2010, MinGW Project So far I've been able to smoothely install many MinGW packages. I found the behavior for mingw-get with no parameter confusiong though: C:\MinGW\bin>mingw-get mingw-get: libexec/mingw-get/gui.exe: unable to start application; status = -1 I see that the behaviour is documented, but I fail to see why this cryptic error message cannot be changed to something helpful. Also I can't see how MSYS packages is going to be installed, although I see it mentioned in the manifest files in MINGW_DIR\var\lib\mingw-get\data. Some questions: Is currently MSYS install supported? Can I add a package to the repository? Is the repository layout documented somewhere? Thanks, regards. |
|
From: Charles W. <cwi...@us...> - 2010-06-18 00:30:58
|
On 6/17/2010 10:02 AM, Stefano Sabatini wrote: > Some questions: > Is currently MSYS install supported? Well...kinda. If you check out a copy of mingw-dist cvs -d:pserver:mingw.cvs.sourceforge.net:/cvsroot/mingw co mingw-dist and "build" it, you'll get a bunch of .xml.lzma files. Put them somewhere safe, and then: > You need a locally installed mingw-get alpha-2, then you must patch > its local manifest cache, to add a package-list reference for this > new manifest file, and confirm that you can install and deploy your > various package components, by executing: > > $ mingw-get install [subsystem-]package-name[-class] Which means you really need to patch the local manifest to list ALL of the .xml.lzma (there are about 75 of them). And then, you might discover that there are bugs/typos/whatnot in the per-package manifests themselves. I hope not, but they really do need testing in order to flush these things out. > Can I add a package to the repository? You, personally? To "THE" repository? Probably not; we don't intend to become the ultimate home of all mingw-ported packages. However, the whole design of mingw-get is so that you can create your OWN repository -- even host one on your own website -- and with suitable .xml.lzma files you can tell your users: "Add this line '...' to your mingw-get top-level manifest file local copy" and run mingw-get..." But...first we need *our* infrastructure up to snuff. Hence...testing of the package manifests we've already written, uploaded, but not yet debugged. For the "official" packages. > Is the repository layout documented somewhere? Err...no. Actually, we're still hashing that out. Which reminds me, I should go ping that thread again. It died last week. -- Chuck |
|
From: Damon R. <dre...@cl...> - 2010-06-18 00:34:08
|
On 6/16/2010 4:43 PM, Keith Marshall wrote: > I've made this point before; no doubt this will not be the last time I > reiterate it: mingw-get is *not* in any way restricted to delivering I don't think he is the only one who missed that one. I am not an expert at this stuff so I get easily confused by information that isn't clear. May I suggest that if http://www.mingw.org/wiki/Getting_Started covered this, you could save yourself from this annoyance? > looking at the MSYS manifests; *you* can help with the validation > process, and so accelerate progress toward publication, or you can > continue to sit back and wait for someone else to do it all, and so > compound the delay. I would love to try but I could use a little help. I am not familiar with your CVS but I think I figured out at least how to get there. I don't know what to do with those files. Could you help me out a little please? Damon Register |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X