From: Paul G. <pga...@qw...> - 2001-03-24 00:31:14
|
Hi folks, On 23 Mar 2001, at 8:49, the Illustrious Earnie Boyd wrote: > Paul Garceau wrote: > > > > Hi folks, > > > > It appears there is a great deal of confusion running around > > about the > > differences between the latest Mingw release vs. the legacy (Mumits > > Mingw32) version. > > Granted, it may be my own confusion, but it is, nonetheless > > painfully > > apparent given a rather extensive exchange of list postings on the > > CrystalSpace mailing list. > > > > [In case anyone was wondering, I am a registered developer for > > CrystalSpace: > > > > http://crystal.linuxgames.com > > > > and am doing development work for a MMORPG, called PlaneShift: > > > > https://sourceforge.net/projects/planeshift/ > > http://www.planeshift.it/ > > > > People who are wanting to download Mingw are, in some cases, > > assuming, > > based on the main web page, http://www.mingw.org, that the latest > > release of Mingw is the same as the Legacy version. Now, we all know > > that this is simply not the case. > > > > Questions: > > > > Should we change the links, in order to negate > > confusion, on the main > > web page so that they reflect the Sourceforge site project file list? > > Or, should we leave the links as they are? > > > > My own possible solution is based on the fact that the current > > releases of the Mingw runtime, etc., are functionally and, based on > > various source code references, fundamentally different than the > > Legacy Mingw32 distributions as listed at Mumits' wisconsin.edu site. > > > > Changing the website would entail re-defining the links that > > are > > currently being referenced. > > > > I would break the page in to two sections: > > > > Legacy -- > > > > This section would only reference Mumits' > > Mingw32 site. > > > > Latest Release -- > > > > This section would only reference links to the > > SourceForge Project Site. > > > > Download -- > > > > If someone wanted to "download", they would go where the > > "Download" > > link takes them (SourceForge site). I might want to change this to > > "Download Latest Release" since that is more accurate given the links > > that come up when "Download" is selected. > > > > No it doesn't take them to the SourceForge site. Forgive me for not being clearer. > I changed that > sometime ago. It takes them to Paul S.'s instructions on what to > download. Yes, it does take them here. The link on the page for "downloads" which references "Standard distribution", however, takes them to the SourceForge site. Given this, perhaps a special link just for installation instructions added at the www.mingw.org site might be all that is needed. > > > However, as it is a major change (I know, "they are just > > links") in > > terms of web site content, I wanted to throw it out here for review > > and hear what everyone had to say about it. > > > > If everyone is in agreement with my proposed solution, I will > > make the > > changes to the web site. > > > > I am looking forward to hearing from everyone. > > > > I'm thinking I don't like it, but work it up under a non-production name > and put it in the trial/htdocs area for us to look at. Don't add it to > CVS just do a copy. I agree that this needs addressed and needs work I > just don't think this is the right approach. I like the one tarball > idea better. Thanks, Earnie. Given that we are in agreement about a single tarball/archive, let me modify the proposal somewhat... first, move installation instructions to Summary of file page and present as a link "Mingw Installation Instructions". http://sourceforge.net/project/showfiles.php?group_id=2435&release_id=15084 second, add a single tarball to the Mingw file list.: (See link above) third, change "download" link to directly reference either main SF project page or the link referenced above. > > Earnie. > > P.S.: For your GCC zip file, upload it to your shell account and make > it group readable. Not sure how to do that with the existing SF web site. Are you saying that I need to do a remote s/o to SF (using my SSH client) and upload to SF that way? Thanks for your consideration on this, Earnie. Peace, Paul G. > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |
From: Paul G. <pga...@qw...> - 2001-03-27 02:29:36
|
Hi folks, On 26 Mar 2001, at 8:03, the Illustrious Earnie Boyd wrote: > Paul Garceau wrote: > > > > Yes, it does take them here. The link on the page for > > "downloads" > > which references "Standard distribution", however, takes them to the > > SourceForge site. > > > > The sidebar and bottombar links must take them to MinGW owned pages > only. This is a standard I've put into place. It ensures consistency. > Also, I like to put a target="_nw" for all href="foo/url" so that the > MinGW window doesn't disappear and become forgotten. I don't expect to change any of that...I am hoping I can accomplish this with simple link changes...nothing more. I will double-check the html links and verify that these settings are there. > > > Given this, perhaps a special link just for installation > > instructions > > added at the www.mingw.org site might be all that is needed. > > > > Ok, write it up and put it in trial/htdocs. > > > > > > > > However, as it is a major change (I know, "they are just > > > > links") in > > > > terms of web site content, I wanted to throw it out here for > > > > review and hear what everyone had to say about it. > > > > > > > > If everyone is in agreement with my proposed solution, I > > > > will make the > > > > changes to the web site. > > > > > > > > I am looking forward to hearing from everyone. > > > > > > > > > > I'm thinking I don't like it, but work it up under a non-production > > > name and put it in the trial/htdocs area for us to look at. Don't > > > add it to CVS just do a copy. I agree that this needs addressed and > > > needs work I just don't think this is the right approach. I like > > > the one tarball idea better. > > > > Thanks, Earnie. > > > > Given that we are in agreement about a single tarball/archive, > > let me > > modify the proposal somewhat... > > > > first, move installation instructions to Summary of file page > > and > > present as a link "Mingw Installation Instructions". > > > > Create the samples for trial/htdocs. > > > http://sourceforge.net/project/showfiles.php?group_id=2435&release_id= > > 15084 > > > > second, add a single tarball to the Mingw file list.: > > (See link above) > > > > third, change "download" link to directly reference either > > main SF > > project page or the link referenced above. > > > > Again the standard I've set is that no sidebar or bottombar link to an > outside source. I won't be changed on this. The thought hadn't crossed my mind...again, I am only wanting to change as little as possible (incidentally, I am a strong believer in changing only what is absolutely required to be changed in order to make something work.) > > > > > > > Earnie. > > > > > > P.S.: For your GCC zip file, upload it to your shell account and > > > make it group readable. > > > > Not sure how to do that with the existing SF web site. Are > > you saying > > that I need to do a remote s/o to SF (using my SSH client) and upload > > to SF that way? > > > > Yes, you can use scp "Secure Copy" or sftp. Ok, thanks for the clarification, Earnie. > > Earnie. Peace, Paul G. > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > MinGW-editor mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-editor > Nothing real can be threatened. Nothing unreal exists. |
From: Earnie B. <ear...@ya...> - 2001-03-26 13:03:02
|
Paul Garceau wrote: > > Yes, it does take them here. The link on the page for "downloads" > which references "Standard distribution", however, takes them to the > SourceForge site. > The sidebar and bottombar links must take them to MinGW owned pages only. This is a standard I've put into place. It ensures consistency. Also, I like to put a target="_nw" for all href="foo/url" so that the MinGW window doesn't disappear and become forgotten. > Given this, perhaps a special link just for installation instructions > added at the www.mingw.org site might be all that is needed. > Ok, write it up and put it in trial/htdocs. > > > > > However, as it is a major change (I know, "they are just > > > links") in > > > terms of web site content, I wanted to throw it out here for review > > > and hear what everyone had to say about it. > > > > > > If everyone is in agreement with my proposed solution, I will > > > make the > > > changes to the web site. > > > > > > I am looking forward to hearing from everyone. > > > > > > > I'm thinking I don't like it, but work it up under a non-production name > > and put it in the trial/htdocs area for us to look at. Don't add it to > > CVS just do a copy. I agree that this needs addressed and needs work I > > just don't think this is the right approach. I like the one tarball > > idea better. > > Thanks, Earnie. > > Given that we are in agreement about a single tarball/archive, let me > modify the proposal somewhat... > > first, move installation instructions to Summary of file page and > present as a link "Mingw Installation Instructions". > Create the samples for trial/htdocs. > http://sourceforge.net/project/showfiles.php?group_id=2435&release_id=15084 > > second, add a single tarball to the Mingw file list.: > (See link above) > > third, change "download" link to directly reference either main SF > project page or the link referenced above. > Again the standard I've set is that no sidebar or bottombar link to an outside source. I won't be changed on this. > > > > Earnie. > > > > P.S.: For your GCC zip file, upload it to your shell account and make > > it group readable. > > Not sure how to do that with the existing SF web site. Are you saying > that I need to do a remote s/o to SF (using my SSH client) and upload > to SF that way? > Yes, you can use scp "Secure Copy" or sftp. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |