Re: WSL-4.0 release candidate

On 16/03/13 20:35, Earnie Boyd wrote:
> Reviewing.  Seems a bit more complicated than necessary

Well, it's not really any more complicated than yours.  If you want
simplicity, just don't abuse mingw-get for this purpose; it is not
designed to handle it.

> and I still don't understand why my idea of a rc_mingwrt and
> rc_w32api packages is bad.

Because it completely trashes mingw-get's bookkeeping.  Because you
advocate simultaneous installation of these two packages alongside the
original mingwrt and w32api packages, whence they deliberately deliver
conflicting content.  How is mingw-get supposed to keep track of that?

> You haven't convinced me yet.

Perhaps you will be convinced, when I address the weakness in mingw-get
which allows you to get away with this sort of misuse in the first
place?  It should be explicitly forbidden.

> +      <licence tarname="mingwrt-%-mingw32-%-dev.tar.%" />
> +      <licence tarname="w32api-%-mingw32-%-dev.tar.%" />
>
> This isn't true for the 4.0 release.
>
> Per previous discussion I added a lic and a doc file.

And that's a trivial adjustment, whether you do it right or persist in
doing it wrong.  I've given you an illustration of how to do it right;
you may adapt that as you see fit.  (Hint: you adjust it within the
updated mingw32-runtime.xml catalogue, which, for the time being, you
distribute only to your candidate testers).

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar