Hi Adrien, yes, I think we should separate between pure toolchain and environment. Eg msys2, cygwin etc. are first hand environments, but of course each of them provides at least one toolchain package. So if we want to provide lists of additional packages available for a specific environment, we should put that into a separate page. Not sure if it should be a separate page for each, or if it is of interest to collect them all on one page. Later could allow to make tables comparing features ... not sure if this is worth the effort.
Cheers, Kai 2015-04-01 9:16 GMT+02:00 Adrien Nader <adr...@notk.org>: > (catching up with my mails LIFO-style, the best way to cause huge > delays) > > On Wed, Mar 25, 2015, Ruben Van Boxem wrote: >> 2015-03-24 21:20 GMT+01:00 Adrien Nader <adr...@notk.org>: >> >> > Hi, >> > >> > On Tue, Mar 24, 2015, David Macek wrote: >> > > On 20. 3. 2015 22:51, Adrien Nader wrote: >> > > > Hi, >> > > > >> > > > I've just pushed a redirect from http://mingw-w64.sourceforge.net to >> > > > http://mingw-w64.yaxm.org in order to serve a new website. >> > > > >> > > > [snip] >> > > > >> > > > Any constructive criticism is welcome; don't hesitate. >> > > >> > > Hi. I took a look on the website and I've got some notes which may or >> > may not be applicable to other visitors: >> > > >> > > === Downloads/Others: >> > > >> > > The first paragraph in the tab talks about OS X builds straight away, as >> > if Others == OSX. This also led to an impression that Rubenv's builds are >> > also for OS X. Also most of the contents of the tab seems to belong to >> > other tabs. I imagine that if a visitor was interested only in toolchains >> > for Windows, he/she could be led to believe that the three options in the >> > first tab were the only one, because he/she would never even look at the >> > Others tab and discovered the link to SF.net file repository. >> > > >> > > The following organisation would make more sense to me: I propose 1) >> > moving Rubenv's builds to the Windows tab, moving the mention of OpenSUSE >> > to the Linux tab, 3) copying the link to SF.net to all relevant tabs (or >> > completely outside of them), and 4) renaming the tab from Other to OS X. I >> > don't think moving these mentions from the Others tab to the other tabs >> > will confuse users as to which one to download, as the gray boxes with >> > logos serve well to make their contents seem as more trust-worthy than the >> > plain text around. >> > >> > The "Others" tab has not received much love and that dates back to the >> > creation of the download page on the previous website. >> > When I put rubenvb and opensuse toolchains back when I created the >> > download page (it's been some time already), the reactions I had >> > received from both upstreams were at best "meh" and without many more >> > details so I couldn't do a lot. I really wanted to put them somewhere >> > though (I think Opensuse's effort started at least 7 years ago and >> > rubenvb toolchains were widespread). Ideally they'd be in a proper >> > place: the "others" section would ideally only contain the link to >> > Sourceforge's FRS. That requires the corresponding toolchain creator to >> > provide information about their releases. >> > >> >> I think I sent you an email with the required info as you asked for way >> back when. If I didn't, my fault, but I'm not too worried about my >> toolchains. They are dated now and should really be retired from the >> download page. > > I don't remember receiving such a mail. Since that was already a fairly > long time ago, I don't remember well but maybe you had sent some infos > but not enough details which was probably quite a lot of work > considering the diversity of your toolchains. > >> > >> > Following Vincent Torri's mail, I did some changes this morning and I >> > just noticed I had not done these changes for every block but only for >> > the ones that fell under Windows and Linux tabs. I've now corrected it. >> > Basically I've removed title elements and added blue-colored blocks >> > instead. They should make it easier to tell each block apart. Can you >> > check the page again and tell me if it looks better? >> > >> > Also, the OS X situation currently is not very good as there is >> > toolchain provider and the toolchains that are available are old, >> > experimental and unsupported. I'm not worrying about it at the moment >> > since it should change soon (more on that later on). >> > >> > > === Downloads/Source: >> > > >> > > This may be just my profession talking, but links to various stuff on >> > SF.net with "SourceForge" as the title seem misleading. >> > > >> > > === Downloads/Linux: >> > > >> > > I know Arch Linux users are generally competent, but I'd like to see the >> > link point to something actually related to mingw-w64, rather than just to >> > AUR homepage. This may be a good link: < >> > https://aur.archlinux.org/packages/?SeB=n&K=mingw-w64&SB=c&PP=250> >> > >> > I'm not an Arch Linux user and the link in place was the only one I had. >> > I've updated the page, thanks. >> > >> > > Also, wouldn't it be better to also mention the packages in official >> > Arch repos? <https://www.archlinux.org/packages/?q=mingw-w64> They don't >> > seem outdated or anything. >> > >> > I wasn't aware of these packages (maybe they're newer than the >> > arch-linux-related update). I'm not sure how they relate to AUR ones; >> > I'm under the impression the toolchain is in the base and non-toolchain >> > packages should be built from AUR but I need a confirmation from at >> > least one actual user. >> > >> >> I can confirm whatever you need: I made the original AUR packages, these >> were absorbed into the binary [Community] repository, and they contain a >> complete toolchain (c,c++,objc,obj-c++,fortran,ada) with the latest >> released versions and is updated regularly. Development versions naturally >> belong in the AUR for which everything is built from source on install. The >> [Community] packages are those you want to link to on the MinGW-w64 >> download page. I'd suggest installing the "mingw-w64-gcc" package, which >> should pull everything else in as a dependency. >> >> Additionally, a couple of users have done the work to provide a bunch of >> libraries in the AUR (which are built from source on install). Someone >> (ant32 and some other guy) even provides binaries in a binary user >> repository: >> https://wiki.archlinux.org/index.php/Unofficial_user_repositories#mingw-w64 >> http://mingw-w64-archlinux.sourceforge.net/ >> >> The build scripts (PKGBUILDs) for them can be found on github: >> https://github.com/ant32/amr >> >> So you can build the non-toolchain packages from the AUR, or get them from >> the user repo linked on the ArchWiki. >> >> Hope this provides enough information. > > Definitely. This is more than enough. Actually I don't know how to fit > all that in the current pages without actually reducing readability. > > I've added the link to the Community packages (that was easy) but the > others would be better on a dedicated page: currently the best way > forward that I can think of is to have the infos for each download set > on a separate page and something much more condensed (only count of > additional packages and everything in a single table). > I'll give that a try whenever I get some free time. > > -- > Adrien Nader > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
