Add debian packaging #32
No reviewers
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/pyceo#32
Loading…
Reference in New Issue
No description provided.
Delete Branch "debian-packaging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #31.
@ -0,0 +6,4 @@
build: docs venv
venv:
I recommend you don't manually set this up and instead add a builddep on https://packages.debian.org/buster/dh-virtualenv
Ooh interesting, I'll take a look.
@ -0,0 +16,4 @@
install:
@# Prepare the virtualenv to be moved (dangerous!)
@# Make sure you don't have '|' in your paths
grep -IRl $(CURDIR)/venv venv | \
Why not define this directly in
debian/rules
?Good idea.
@ -225,0 +239,4 @@
To build unsigned packages:
```sh
gbp buildpackage --git-ignore-new --git-upstream-tree=BRANCH --git-upstream-branch=master -uc -us
You can avoid a bunch of these CLI flags by adding a gbp.conf, ala https://salsa.debian.org/clojure-team/clojure/-/blob/main/debian/gbp.conf
Thanks, I'll give it a try.
@ -0,0 +3,4 @@
Section: admin
Priority: optional
Standards-Version: 4.3.0
Vcs-Git: https://git.csclub.uwaterloo.ca/public/pyceo.git
If you care about a policy-compliant control file, lintian would catch that you're missing
Vcs-Browser
Good catch.
@ -0,0 +44,4 @@
Package: ceo
Architecture: amd64
Replaces: ceo-python, ceo-clients
Conflicts: ceo-python, ceo-clients
Why does this have Replaces/Conflicts? Do these packages actually exist?
Yes, there are the old ceo client packages. We want to make sure that they're removed before installing the new one.