0

I currently am using this guide to package up my project wasp. However currently everything lives inside of the wasp file.

That's not ideal. I would rather have all the classes in separate files so it can be more effectively managed. I have the series of files needed in the debian directory. But I'm not sure how to configure the packaging to package multiple files.

Is there a way to change my packaging to package more than just the one script file?

asked Sep 22, 2017 at 13:36

1 Answer 1

1

I'm not a debian package or Python expert, but one way would be to copy the various source files to another location (outside of /usr/bin), and then have /usr/bin/wasp call out to them.

Say you put all of your python code in src/ in the root of your repo. In the debian/install file, you'd have:

wasp usr/bin
src/* usr/lib/wasp/

You'd then just need /usr/bin/wasp to call some entry point in src. For example,

#!/usr/bin/python3
import sys
sys.path.append('/usr/lib/wasp/')
import wasp # or whatever you expose in src
# ...

Again, I don't know the best practices here (either in directory or python usage) but I think this would at least work!

answered Sep 29, 2017 at 0:47
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.