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.

>
> 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.

Ruben


>
> > === Downloads/Windows:
> >
> > Mentioning Cygwin while omitting MSYS2 seems weird, given the numbers of
> packages they provide. I'm definitely in favor of mentioning MSYS2 in this
> tab. Is there a reason Cygwin is first in this list?
>
> Jonathan gave me the relevant information and, to the best of my
> knowledge, it is still (mostly) correct.
>
> There's an additional reason: I'm seeing cygwin similarly to
> fedora/opensuse/arch.
> If someone is already using these, the entries on the website will make
> him check his version requirements and look at his distro package
> manager. They probably won't make anyone start using these distros
> however. Some distros have recent versions, some don't (debian, ubuntu)
> and I believe this page can help the user by providing something simple
> to read.
>
> MSYS2 is different in that there's a lot more to say. I also don't want
> to make all the content myself and had had no actual feedback on that
> front before.
>
> Cygwin is first because the lists are sorted alphabetically. I don't
> think I want to start changing that.
>
> > ===
> >
> > Overall, the website looks very good IMO.
>
> Good to hear. :)
>
> > I noticed some typos and weird sentences in some places; should I also
> note them here on the ML?
>
> I can either create you an account on the wiki or you can send me the
> list of things to change and I'll review and apply.
>
> --
> 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

Reply via email to