Re: [PATCH cygport 0/2] Add provides: and conflicts:

On Sat, 2020-02-08 at 13:46 +, Jon Turney wrote: > Add the ability to specify provides: and conflicts: hints in the cygport. > > Jon Turney (2): > Add test which compares hints with expected > Add provides: and conflicts: hints > > lib/pkg_pkg.cygpart | 74

Re: [PATCH cygport 0/2] Use meson auto-features option

On Tue, 2019-04-02 at 18:21 +0100, Jon Turney wrote: > Jon Turney (2): > meson: use auto-features option > Fixup __version_at_least a bit > > cygclass/meson.cygclass | 9 - > lib/check_funcs.cygpart | 6 +++--- > 2 files changed, 11 insertions(+), 4 deletions(-) Pushed to master,

Re: [PATCH cygport] Raise an error if we package a .stackdump file

On Fri, 2018-07-13 at 17:15 +0100, Jon Turney wrote: > If we end up with a .stackdump file in a package, this tends to suggest > something has gone wrong somewhere, so raise an error. > --- > lib/pkg_pkg.cygpart | 9 - > 1 file changed, 8 insertions(+), 1 deletion(-) Pushed to master,

Re: [PATCH cygport 0/2] Better handling of build depends

On Tue, 2017-10-03 at 20:53 +0100, Jon Turney wrote: > Jon Turney (2): > Rename DEPEND to BUILD_DEPENDS > Pass BUILD_DEPENDS through to .hint for source package as > build-depends: > > lib/check_funcs.cygpart | 17 - > lib/pkg_pkg.cygpart | 5 + > 2 files

Re: [PATCH cygport 0/3] Don't allow source packages to differ by arch

On Tue, 2018-02-13 at 13:12 +, Jon Turney wrote: > This is where I got to, after the discussion at [1]. > > [1] https://cygwin.com/ml/cygwin-apps/2017-05/msg00050.html > > Jon Turney (3): > Document src_unpack_hook and src_patch_hook > Add src_patch_apply_hook > Don't allow SRC_URI or

Re: Putting packages up for adoption

On Mon, 2020-03-23 at 22:04 +0100, Jan Nijtmans wrote: > Op ma 23 mrt. 2020 om 16:45 schreef Yaakov Selkowitz: > > The bulk of the patchset is from Fedora, but they haven't updated > > recently either. > > Hm. It appears that they did: >

Re: Putting packages up for adoption

Am 23.03.2020 um 18:14 schrieb ASSI: Achim Gratz writes: I currently have that stack in evaluation (since Pango needs those). It looks like I have most or all of the needed development libraries in my installation already. If that also holds true for the rest of the Gtk2 modules I'll just

Re: Putting packages up for adoption

Op ma 23 mrt. 2020 om 16:45 schreef Yaakov Selkowitz: > The bulk of the patchset is from Fedora, but they haven't updated > recently either. Hm. It appears that they did: :-) Regards, Jan Nijtmans

Re: Putting packages up for adoption

Achim Gratz writes: > I currently have that stack in evaluation (since Pango needs those). It > looks like I have most or all of the needed development libraries in my > installation already. If that also holds true for the rest of the Gtk2 > modules I'll just take them all… I'll look at Gtk3

Re: Putting packages up for adoption

On Mon, 2020-03-23 at 13:07 +0100, Jan Nijtmans wrote: > Op zo 22 mrt. 2020 om 23:34 schreef Yaakov Selkowitz: > > A word of caution wrt Tcl/Tk for Cygwin: upstream incorrectly treats > > Cygwin as a Win32 platform, necessitating extensive patches to make it > > comply with *NIX/X11 standards.

Re: Putting packages up for adoption

Op zo 22 mrt. 2020 om 23:34 schreef Yaakov Selkowitz: > A word of caution wrt Tcl/Tk for Cygwin: upstream incorrectly treats > Cygwin as a Win32 platform, necessitating extensive patches to make it > comply with *NIX/X11 standards. These patches CANNOT be dropped > without breaking compatibility,