-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: debian package update #48
Conversation
no need to abuse the pwd shell command, we have a handy DESTDIR variable, which the makefile should respect too. but because we need to pass PREFIX anyways (since we need to override the correct upstream default, /usr/local) it's probably not worth implementing DESTDIR in the Makefile...
okay, i think i'm about done here - the only WIP left here is the question of the CHANGES vs debian/changelog files... |
@SaveTheRbtz was the one that originally packaged this in hoytech#1, i thought it was upstream...
Thank you! Let's not do a systemd unit file for now. My only concern is, as you mentioned, the CHANGES/changelog split. I'd really prefer not maintaining 2 of them, and if possible not breaking the existing format. Is the format you've created required by debian? |
I see you added instructions on how to maintain the changelog file in the PR. I'm merging your branch now, thanks again! |
those are the changes I was thinking about in #47.
most of those are minor maintenance changes that you won't need to do in the future. only changes like 36e013d would be necessary on a regular basis.
as you can see, you will need to decide if you use
debian/changelog
orCHANGES
as your main changelog. in my native packages, i just symlink the two together (example) and maintain everything indebian/changelog
, but you may not like the format.also note that the 1.2.1 release is marked as UNRELEASED. this means the release is not completed just yet, and tools (like
gbp dch
) will keep on adding new entries from your git history (automatically!) when you add stuff to the history.another improvement that could be done would be to ship a systemd
.service
file, since it makes it easier to manage the service since Debian jessie.init.d
files still work, of course, and we can keep on shipping it for those users who do not want or cannot run systemd... it would also be useful for other distros.