Package Details: mingw-w64-glib2 2.80.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-glib2.git (read-only, click to copy)
Package Base: mingw-w64-glib2
Description: Low level core library (mingw-w64)
Upstream URL: https://wiki.gnome.org/Projects/GLib
Keywords: glib2 gnome gtk gtk2 gtk3 mingw mingw-w64
Licenses: LGPL2.1
Submitter: brcha
Maintainer: drakkan
Last Packager: drakkan
Votes: 20
Popularity: 0.000000
First Submitted: 2012-06-13 19:15 (UTC)
Last Updated: 2024-03-28 08:23 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 9 Next › Last »

drakkan commented on 2020-05-19 13:21 (UTC)

OK, I'll add a NO_EXECUTABLES env var here too, thanks for the suggestion

Martchus commented on 2020-05-19 12:55 (UTC) (edited on 2020-05-19 13:57 (UTC) by Martchus)

I don't need the executables of this particular package so the decision isn't very important to me. Generally it seems wrong to delete them just to save a few KiB on my floppy disk because they might be useful at some point after all. So far I've just ignored executables I didn't need and I don't see any problem with that.

By the way, the whole "let's not blindly delete all executables" idea came up when I started to use x264, x265 and ffmpeg. The executables contained by these packages are indeed useful to have. Even if ffmpeg isn't used directly after all it can be quite useful for checking quickly whether the libraries work. Maybe the same applies to other packages as well.

So from my point of view we should not have a general "keep EXEs" or "delete EXEs" rule which should be applied to all packages. Since EXEs can be useful I'd like to keep them in doubt but if really nobody uses them (which might be the case in this package) I have nothing against deleting them. By the way, the Qt 5 packages use the NO_EXECUTABLES environment variable to decide whether to keep EXEs so that's also an option.

If you decide to remove EXEs in your packages, please do not bump the pkgrel in this case. I find it unnecessary to rebuild packages just to remove EXEs.

drakkan commented on 2020-05-19 11:19 (UTC)

@xantares, no problem to remove the exes, but are we sure that noone need them? I use glib as gstreamer dependency so I don't need exes but executables like glib-compile-resources could be useful. @Martchus, @other, do you agree to remove exes from this PKGBUILD (and others that I maintain?), thanks!

xantares commented on 2020-05-19 08:00 (UTC)

ok. could we remove the exes please ?

Martchus commented on 2020-05-18 09:00 (UTC)

I don't have a problem with using Git. Once one cloned it one just needs to fetch what's new so it isn't that bad and might even speed up subsequent updates.

And yes, if nothing speaks against it, it makes sense to follow what the official/regular PKGBUILDs do.

drakkan commented on 2020-05-18 07:16 (UTC) (edited on 2020-05-18 07:17 (UTC) by drakkan)

@xantares, git clones are used in the PKGBUILD in the official Arch Linux repo too. Aren't we supposed to be as close as possible to the PKGs in the official repos?

xantares commented on 2020-05-18 06:52 (UTC)

can the source be changed to use the tarball, git clone takes forever:

https://download.gnome.org/sources/glib/2.64/

drakkan commented on 2018-09-23 18:00 (UTC)

@Martchus thanks!

I have some more changes to test

http://94.177.162.225/temp/mingw-w64-glib2/PKGBUILD http://94.177.162.225/temp/mingw-w64-glib2/0001-Use-CreateFile-on-Win32-to-make-sure-g_unlink-always.patch http://94.177.162.225/temp/mingw-w64-glib2/0001-win32-Make-the-static-build-work-with-MinGW-when-pos.patch

this PKGBUULD compiles, but I would like to do some more testing before push upstream

Martchus commented on 2018-09-23 16:58 (UTC)

I've rebuilt the package (using this PKGBUILD). Let's see whether Qt 5 builds now. As soon as mingw-w64-qt5-declarative appears in my repo you can assume it worked :-)

« First ‹ Previous 1 2 3 4 5 6 7 .. 9 Next › Last »