So, to the important issue of whether a quickly app depends on quickly or not, it definitely does not. During development, yes it does. But if you run "quickly package", it will create a deb file that does not depend on quickly.
The problem is that some files like schemas and images and such need to either be in a certain place on disk (requiring root access and messing with your system) or need various environmental variables set to point at the right places.
So that's what the wrapper script does. It has two modes (running as developer and running on system -- i.e. 'quickly run' or 'quickly package').
So it sounds like this bug is really about PyDev and quickly not having good integration?
So, to the important issue of whether a quickly app depends on quickly or not, it definitely does not. During development, yes it does. But if you run "quickly package", it will create a deb file that does not depend on quickly.
The problem is that some files like schemas and images and such need to either be in a certain place on disk (requiring root access and messing with your system) or need various environmental variables set to point at the right places.
So that's what the wrapper script does. It has two modes (running as developer and running on system -- i.e. 'quickly run' or 'quickly package').
So it sounds like this bug is really about PyDev and quickly not having good integration?