The reason for having the standard provides at all, or the reason they
are in mingw-filesystem? The reason for having them at all is just
for uniformity. You can "BuildRequires: mingw(wsock32.dll)" and not
care whether that comes from Windows/Wine or from Fedora.
The reason they are in mingw
On 03.05.22 17:16, Richard W.M. Jones wrote:
On Tue, May 03, 2022 at 04:46:34PM +0200, Sandro Mani wrote:
Any comments/objections?
That seems to make sense to me, is there a reason why it wasn't before?
As far as I see mingw-filesystem provided the standard DLLs since
the beginning of the
On Tue, May 03, 2022 at 04:46:34PM +0200, Sandro Mani wrote:
>
> >>Any comments/objections?
> >>
> >>
> >>That seems to make sense to me, is there a reason why it wasn't before?
> >>
> As far as I see mingw-filesystem provided the standard DLLs since
> the beginning of the package, perhaps @rjones
Any comments/objections?
That seems to make sense to me, is there a reason why it wasn't before?
As far as I see mingw-filesystem provided the standard DLLs since the
beginning of the package, perhaps @rjones can recall if there was a reason?
___
t; ")
> Provides: mingw64(mscoree.dll)
>
> %package -n ucrt64-filesystem
> [...]
> Provides: %(sed "s/\(.*\)/ucrt64(\1) /g" %{SOURCE22} | tr "\n" " ")
> Provides: ucrt64(mscoree.dll)
>
>
> I wonder whether these stan
age -n mingw64-filesystem
[...]
Provides: %(sed "s/\(.*\)/mingw64(\1) /g" %{SOURCE21} | tr "\n" " ")
Provides: mingw64(mscoree.dll)
%package -n ucrt64-filesystem
[...]
Provides: %(sed "s/\(.*\)/ucrt64(\1) /g" %{SOURCE22} | tr "\n" "
