zdohnal
zdohnal
@michaelrsweet > I'm not comfortable separating the "registration hostname" from the "listen hostname". > Hmm... I meant registration hostname to be exactly the listen hostname - and we have to...
I've removed public accessors and renamed reghost to listen_hostname - it is set only when ```papplSystemAddListeners()``` is called. I set the PR to [WIP], until it is clear how I...
@michaelrsweet ad saving listen-hostname - Or did you mean to save listen-hostname into ```system->hostname``` in ```papplSystemAddListeners()```? That's another way how I imagine to keep the hostnames in sync, but I'm...
Ignore the review request for now, I rewrite it to use ```system->hostname```. Once it is ready, I remove the [WIP].
Ready for review.
@michaelrsweet ping
Hmm... it can work, although it would be great if PAPPL could adapt a feature which I know from systemd - that ```/etc/lprint.conf``` is only for admin/maintainers overrides of default...
> I personally hate this behavior - because different distros (and versions of systemd) move where these files live, it is almost impossible to know how to customize the configuration...
But to mention - I don't mind having those settings in a configuration file. I made the PR based on my current knowledge that some of options are available only...
> The system state file is normally stored in /var/lib/BASENAME.state. For snaps this becomes $SNAP_COMMON/BASENAME.state. For per-user instances it depends on the environment but can be ~/.config/BASENAME.state, ~/Library/Application Support/BASENAME.state, or...