You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has come to my attention that PAPPL 1.4's new option support conflicts with the historical state filenames for lprint (lprint.conf).
In order to separate configuration/state from options, PAPPL by default uses BASENAME.state for state and printer configuration and BASENAME.conf for server configuration (read-only). LPrint needs to migrate to the new file naming conventions and ideally should stop using its own system callback now that the default is fully functional.
The text was updated successfully, but these errors were encountered:
Hopefully we won't run into too many cases where the lprint.conf filename would have been used. The new system callback follows PAPPL's method (which follows the corresponding platform standards...):
[master 648bc20] Update state filename to current PAPPL standard, rename old state filenames (Issue #129)
It has come to my attention that PAPPL 1.4's new option support conflicts with the historical state filenames for lprint (lprint.conf).
In order to separate configuration/state from options, PAPPL by default uses BASENAME.state for state and printer configuration and BASENAME.conf for server configuration (read-only). LPrint needs to migrate to the new file naming conventions and ideally should stop using its own system callback now that the default is fully functional.
The text was updated successfully, but these errors were encountered: