[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1112646: elpa-ligature: support emacs-pgtk



Package: elpa-ligature
Version: 1.0~git20231203.6ac1634-2
Severity: wishlist

Dear Maintainer,

the package description states "It though only works with Debian's emacs-gtk
package.", and the metadata enforces that: "Depends: emacs-gtk".  I am not using
emacs-gtk, but emacs-pgtk, which conflicts with emacs-gtk.  I thus cannot
install elpa-ligature, without removing emacs-pgtk.
Copying the package's files into my $HOME and manually loading them from within
emacs-pgtk does however seem to work.  Is there some known issue with
elpa-ligature and emacs-pgtk, that I've yet to notice?  In that case it might be
nice to change the description to "It only works with Debian's emacs-gtk, not
emacs-pgtk.", to make it clear that this packages does not just need a GTK GUI
(which was my first interpretation of what that description intended to say),
but specifically emacs-gtk.
Otherwise, would it be possible to e.g. change the "Depends:" to "emacs-gtk |
emacs-pgtk", to allow installation of elpa-ligature alongside emacs-pgtk?


Yours
Timon


-- System Information:
Debian Release: forky/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.16.3+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-ligature depends on:
ii  dh-elpa-helper  2.1.9
pn  emacs-gtk       <none>
ii  emacsen-common  3.0.8
ii  libcairo2       1.18.4-1+b1

Versions of packages elpa-ligature recommends:
ii  fonts-firacode  6.2-3
ii  fonts-nanum     20250212-1

Versions of packages elpa-ligature suggests:
pn  fonts-cascadia-code   <none>
pn  fonts-fantasque-sans  <none>
ii  fonts-firacode        6.2-3
pn  fonts-jetbrains-mono  <none>
pn  fonts-monoid          <none>
ii  fonts-nanum           20250212-1
pn  fonts-naver-d2coding  <none>


Reply to: