> On Aug. 16, 2015, 12:33 p.m., Patrick von Reth wrote: > > Win32libs should always use a tag if possible. > > Is there any up to date tarball?
Hmm, how do I specify a tag and not a branch? I think branch 0.7 is functioning as the most recent MSVC-compatible version. Right now it looks like the latest tag 0.7.4 corresponds to the tarball on the website, but that is a now a very old release. (May 2014) If it's possible to overlook a lapse in binary compatibility until Vc 1.0 comes out, I think it would be a good candidate to bend this rule: first because Vc is essentially header-only, and second because Krita is essentially the only user of the library. - Michael ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124756/#review83881 ----------------------------------------------------------- On Aug. 15, 2015, 10:40 p.m., Michael Abrahams wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/124756/ > ----------------------------------------------------------- > > (Updated Aug. 15, 2015, 10:40 p.m.) > > > Review request for kdewin. > > > Repository: emerge > > > Description > ------- > > This continues to use the older version 0.7 which is supported on MSVC. > > > Diffs > ----- > > portage/win32libs/vc/vc.py 1e02192 > > Diff: https://git.reviewboard.kde.org/r/124756/diff/ > > > Testing > ------- > > > Thanks, > > Michael Abrahams > >
_______________________________________________ Kde-windows mailing list Kde-windows@kde.org https://mail.kde.org/mailman/listinfo/kde-windows
