Bug#914568: emacs25: Please build with xwidget support
Hi, > FWIW, I would not be enthusiastic about 2.b. I think the > converse issue > of people upgrading to xwidgets support would not necessarily be > desirable. That's a fair observation I hadn't thought about. 2.b's out, then. Thanks for considering, -d
Bug#914568: emacs25: Please build with xwidget support
Dato Simó writes: > 1. have a separate emacs-xwidgets _source_ package, confined to > unstable. > > 2. ‘abuse’ the experimental suite, and re-upload there every > unstable version verbatim, with xwidgets support > > 2.a: ... in a separate emacs-xwidgets package, OR > 2.b: ... in the main emacs package > > (2.a) would need checking with ftpmaster, just to be sure they're > okay; (2.b) is simpler but misleading (upgrading from experimental > to a higher version in unstable will _lose_ you features). (1) is > typically frowned upon. FWIW, I would not be enthusiastic about 2.b. I think the converse issue of people upgrading to xwidgets support would not necessarily be desirable. d
Bug#914568: emacs25: Please build with xwidget support
> check-security-status also says webkit2gtk is unsupported. So unless I > miss something, nothing has significantly changed with respect to > xwidgets. Okay, fair enough. It would still be nice, though, to have an emacs-xwidgets package. Unfortunately, it is not feasible to have it built in unstable from the ‘emacs’ source package, because it would have to migrate to testing; it's not possible to migrate a subset of binary packages. Two options I can think of are: 1. have a separate emacs-xwidgets _source_ package, confined to unstable. 2. ‘abuse’ the experimental suite, and re-upload there every unstable version verbatim, with xwidgets support 2.a: ... in a separate emacs-xwidgets package, OR 2.b: ... in the main emacs package (2.a) would need checking with ftpmaster, just to be sure they're okay; (2.b) is simpler but misleading (upgrading from experimental to a higher version in unstable will _lose_ you features). (1) is typically frowned upon. Just to be clear, I can volunteer to make these uploads if needed. I'm rebuilding form myself anyway. Cheers, -d
Bug#914568: emacs25: Please build with xwidget support
Dato writes: > Hi, > > On Sun, Nov 25, 2018 at 11:40 -0600, Rob Browning wrote: > >> Assuming those concerns are still valid, then I suspect we wouldn't want >> to (re)enable support in the primary package, and if we did eventually >> provide some kind of support, it should be solidly opt-in. > > Emacs >= 26.1 builds with the new (4.0) libwebkit2gtk API which, > to the best of my knowledge is supported. At least, it's in buster > with no serious bugs. (It's a different source package than the > one mentioned in #843462.) > > Seems it could be a good time to re-introduce xwidgets support in > Emacs? check-security-status also says webkit2gtk is unsupported. So unless I miss something, nothing has significantly changed with respect to xwidgets. d
Bug#914568: emacs25: Please build with xwidget support
Hi, On Sun, Nov 25, 2018 at 11:40 -0600, Rob Browning wrote: > Assuming those concerns are still valid, then I suspect we wouldn't want > to (re)enable support in the primary package, and if we did eventually > provide some kind of support, it should be solidly opt-in. Emacs >= 26.1 builds with the new (4.0) libwebkit2gtk API which, to the best of my knowledge is supported. At least, it's in buster with no serious bugs. (It's a different source package than the one mentioned in #843462.) Seems it could be a good time to re-introduce xwidgets support in Emacs? It'd be greatly appreciated. Thanks for considering, -d
Bug#914568: emacs25: Please build with xwidget support
John Goerzen writes: > Over at > https://www.gnu.org/software/emacs/manual/html_node/emacs/Embedded-WebKit-Widgets.html > , the xwidget-webkit-browse-url function is documented. > > C-h a also lists it, and it is apparently defined in xwidget.el. > > However, when I run M-x xwidget-webkit-browse-url, I get: "Your Emacs > was not compiled with xwidgets support" Ahh, so that's intentional; from the Debian changelog: * Disable xwidget (webkit) support. Thanks to David Bremner for reporting the issue. (Closes: 843462) i.e. https://bugs.debian.org/843462 Assuming those concerns are still valid, then I suspect we wouldn't want to (re)enable support in the primary package, and if we did eventually provide some kind of support, it should be solidly opt-in. If there's no simpler option (i.e. a reliable, upstream enable-webkit-support defcustom or something) I suppose we could consider providing a new package flavor, but first we'd need to decide that the benefit was worth the extra cost/complexity. In the shorter term, if it's feasible you could build local packages after installing libwebkitgtk-3.0-dev and adding: confflags_gtk += --with-xwidgets to debian/rules (or in the older emacsXY packages): confflags_x += --with-xwidgets Then, the resulting emacs (or emacsXY) package should have support. Of course, we could also try to make that easier to build. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#914568: emacs25: Please build with xwidget support
Package: emacs25 Version: 25.1+1-4+deb9u1 Severity: normal Hi, Over at https://www.gnu.org/software/emacs/manual/html_node/emacs/Embedded-WebKit-Widgets.html , the xwidget-webkit-browse-url function is documented. C-h a also lists it, and it is apparently defined in xwidget.el. However, when I run M-x xwidget-webkit-browse-url, I get: "Your Emacs was not compiled with xwidgets support" Thanks, John -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages emacs25 depends on: ii emacs25-bin-common 25.1+1-4+deb9u1 ii gconf-service 3.2.6-4+b1 ii libacl12.2.52-3+b1 ii libasound2 1.1.3-5 ii libatk1.0-02.22.0-1 ii libc6 2.24-11+deb9u3 ii libcairo-gobject2 1.14.8-1 ii libcairo2 1.14.8-1 ii libdbus-1-31.10.26-0+deb9u1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgconf-2-4 3.2.6-4+b1 ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2 ii libgif75.1.4-0.4 ii libglib2.0-0 2.50.3-2 ii libgnutls303.5.8-5+deb9u3 ii libgomp1 6.3.0-18+deb9u1 ii libgpm21.20.4-6.2+b1 ii libgtk-3-0 3.22.11-1 ii libice62:1.0.9-2 ii libjpeg62-turbo1:1.5.1-2 ii libm17n-0 1.7.0-3+b1 ii libmagickcore-6.q16-3 8:6.9.7.4+dfsg-11+deb9u5 ii libmagickwand-6.q16-3 8:6.9.7.4+dfsg-11+deb9u5 ii libotf00.9.13-3+b1 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-01.40.5-1 ii libpng16-161.6.28-1 ii librsvg2-2 2.40.16-1+b1 ii libselinux12.6-3+b3 ii libsm6 2:1.2.2-1+b3 ii libtiff5 4.0.8-2+deb9u2 ii libtinfo5 6.0+20161126-1+deb9u2 ii libx11-6 2:1.6.4-3 ii libx11-xcb12:1.6.4-3 ii libxcb11.12-1 ii libxfixes3 1:5.0.3-1 ii libxft22.3.2-1+b2 ii libxinerama1 2:1.1.3-1+b3 ii libxml22.9.4+dfsg1-2.2+deb9u2 ii libxpm41:3.5.12-1 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii zlib1g 1:1.2.8.dfsg-5 emacs25 recommends no packages. Versions of packages emacs25 suggests: ii emacs25-common-non-dfsg 25.1+1-1 -- no debconf information
