FS#74728 - [pinentry] Split package to pinentry-curses, pinentry-qt, etc....
Attached to Project:
Arch Linux
Opened by Daniele Basso (tiziodcaio) - Friday, 13 May 2022, 14:27 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:23 GMT
Opened by Daniele Basso (tiziodcaio) - Friday, 13 May 2022, 14:27 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:23 GMT
|
Details
Might be interesting splitting the package into smaller one
to let the user to chose which one he needs?
|
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:23 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/pinentry/issues/4
Saturday, 25 November 2023, 20:23 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/pinentry/issues/4
Comment by Toolybird (Toolybird) -
Wednesday, 27 July 2022, 08:57 GMT
Comment by
Daniele Basso (tiziodcaio) -
Tuesday, 02 August 2022, 08:35 GMT
Comment by
Alexander F. Rødseth (xyproto) -
Friday, 16 September 2022, 13:34 GMT
What, you mean like Debian, Fedora, etc? Not sure it's worth it
with our current optdepends arrangement..
Maybe simply adding a provide field to all the split packages so
when installing pinentry asks which pinentry-frontend should I
install... Would not works?
Splitting the package so that GTK2 is no longer needed in any
package in [core] might be a good idea.