Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make zint backend required by default , and allow "--without-zint" only when flag set explicitly #20

Open
gwpl opened this issue Feb 1, 2017 · 0 comments

Comments

@gwpl
Copy link

gwpl commented Feb 1, 2017

Hi!
I find zint backend crucial for good user experience for someone giving a try to glabels-3!
It provides so many barcodes types!

I found saidly that because it's optional by default, in many distributions users struggled with getting packaged with zint support compiled in - e.g. for some period of time in Ubuntu, now I struggle also in Archlinux. I am skilled, so despite inconvenience I can rebuild package on my own, but not all users are so eager, especially if they want to give a try to application -> it's high risk they may discard after seeing few barcode options available by default.

Therefore, I highly suggest to perform in following way to give a signal to package maintainers (of all distros) as same time :

  • make zint required by default
  • in case of lack of zint, make ./configure to display message "zint is highly recommended for good user experience, due to amount of barcodes it's provides. Although, it's possible to compile glabels-3 without zint. To do so, set '--without-all-what-zint-provides-I-am-sure' flag, but only if you are sure."

Ok, maybe I exaggerated a bit with name of flag ;) , but I hope I show my point.
I am just afraid that most package maintainers automatically compile thousands of packages never looking at them more carefully, so there is no chance they will add any optional dependency if it does not break fully automatic build and require human intervention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant