public
/
pyceo
26
1
Fork 3
Code Issues 26 Pull Requests 5 Projects Releases 1 Wiki Activity

Add debian packaging #32

Merged
merenber merged 2 commits from debian-packaging into v1 2021-10-28 20:52:20 -04:00
Conversation 0 Commits 2 Files Changed 31
merenber commented 2021-10-28 20:25:37 -04:00
repo.issues.owner

Closes #31.

Closes #31.
merenber added 2 commits 2021-10-28 20:25:38 -04:00
continuous-integration/drone/pr Build is passing Details
3019b424be fix manpages
merenber merged commit 02aff43e7f into v1 2021-10-28 20:52:20 -04:00
merenber referenced this issue from a commit 2021-10-28 20:52:20 -04:00
Add debian packaging (#32)
merenber deleted branch debian-packaging 2021-10-28 20:52:25 -04:00
ehashman reviewed 2021-10-28 21:12:05 -04:00
Makefile
@ -0,0 +6,4 @@
build: docs venv
venv:
ehashman commented 2021-10-28 21:05:00 -04:00
repo.issues.owner

I recommend you don't manually set this up and instead add a builddep on https://packages.debian.org/buster/dh-virtualenv

I recommend you don't manually set this up and instead add a builddep on https://packages.debian.org/buster/dh-virtualenv
merenber commented 2021-10-28 21:40:54 -04:00
repo.issues.poster
repo.issues.owner

Ooh interesting, I'll take a look.

Ooh interesting, I'll take a look.
Makefile
@ -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 | \
ehashman commented 2021-10-28 21:05:34 -04:00
repo.issues.owner

Why not define this directly in debian/rules?

Why not define this directly in `debian/rules`?
merenber commented 2021-10-28 21:41:11 -04:00
repo.issues.poster
repo.issues.owner

Good idea.

Good idea.
README.md
@ -225,0 +239,4 @@
To build unsigned packages:
```sh
gbp buildpackage --git-ignore-new --git-upstream-tree=BRANCH --git-upstream-branch=master -uc -us
ehashman commented 2021-10-28 21:07:16 -04:00
repo.issues.owner

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

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
merenber commented 2021-10-28 21:42:01 -04:00
repo.issues.poster
repo.issues.owner

Thanks, I'll give it a try.

Thanks, I'll give it a try.
debian/control
@ -0,0 +3,4 @@
Section: admin
Priority: optional
Standards-Version: 4.3.0
Vcs-Git: https://git.csclub.uwaterloo.ca/public/pyceo.git
ehashman commented 2021-10-28 21:09:25 -04:00
repo.issues.owner

If you care about a policy-compliant control file, lintian would catch that you're missing Vcs-Browser

If you care about a policy-compliant control file, lintian would catch that you're missing `Vcs-Browser`
merenber commented 2021-10-28 21:43:17 -04:00
repo.issues.poster
repo.issues.owner

Good catch.

Good catch.
debian/control
@ -0,0 +44,4 @@
Package: ceo
Architecture: amd64
Replaces: ceo-python, ceo-clients
Conflicts: ceo-python, ceo-clients
ehashman commented 2021-10-28 21:11:09 -04:00
repo.issues.owner

Why does this have Replaces/Conflicts? Do these packages actually exist?

Why does this have Replaces/Conflicts? Do these packages actually exist?
merenber commented 2021-10-28 21:43:44 -04:00
repo.issues.poster
repo.issues.owner

Yes, there are the old ceo client packages. We want to make sure that they're removed before installing the new one.

Yes, there are the old ceo client packages. We want to make sure that they're removed before installing the new one.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
priority
high
High priority   
priority
low
Low priority   
priority
medium
Medium priority   
priority
very high
Very high priority
No Label
priority
high
priority
low
priority
medium
priority
very high
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/pyceo#32
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?