Create a -cli package without a different executable

[Nicoleau Fabien]

Hi,

I'm packaging phatch that provides /usr/bin/phatch, a graphical
application to manage some operations on photos. It handles command
line parameters so that it can be used in a script, without a GUI :
if no parameters are given, a GUI is displayed, otherwise it acts as a
console application.

Upstream asked me if it's possible to keep "phatch" package, containing
the graphical requirements (and requires) and requires phatch-cli, and
create a phatch-cli, that provides /usr/bin/phatch. With this way,
people could just install phatch-cli on a server and use it with
command line parameters (but it would crash if it's not launched with
parameters).

My question is :
is it good to provide a -cli package that does not provides a separate
script or executable file, and that will work only if the user is
carefull to not launch it in a way that it does not require a graphic
lib (without parameters in that context) ?


Regards,

Fabien NICOLEAU