Year/version updates, Pt 1 Packaging Fix - v.0.5.6

mailchuck / PyBitmessage

This repository has been discontinued, please use the official PyBitmessage repository

https://github.com/Bitmessage/PyBitmessage

MIT License

28 stars 4 forks source link

Year/version updates, Pt 1 Packaging Fix - v.0.5.6 #158

Open mendaxi opened 8 years ago

mendaxi commented 8 years ago

Changes the Year and Version numbers to be up-to-date.

Highlights:

Changes all instances of the Version no. ".0.4.4" except in prev. ver. variables to ".0.5.6"
Changes the copyright/license expiration from 2014 to 2016
Removes ebuild.sh as mentioned in #139
Signed commits (I think) - what a relief!

mendaxi commented 8 years ago

Oh yes, I almost forgot:

Fixes the debian packaging error in #139 with the following code in debian.sh

CURDIR=`pwd`
SHORTDIR=`basename ${CURDIR}`

# Intelligently detects current dir name and changes accordingly
mv ../${SHORTDIR} ../${DIR}

dpkg-buildpackage -F -us -uc

# This does not work if you don't have a private signing key
# To change it back, uncomment the next two lines.
#gpg -ba ../${APP}_${VERSION}-1_${ARCH_TYPE}.deb
#gpg -ba ../${APP}_${VERSION}.orig.tar.gz

# Restores back to the parent dir name that was established with the SHORTDIR and CURDIR vars
mv ../${DIR} ../${SHORTDIR}

mendaxi commented 8 years ago

However, with these changes, there needs to be a build dependency list update, because it will give you errors if you try to build from a clean OS.

PeterSurda commented 8 years ago

I thought I removed ebuild.sh already?

mendaxi commented 8 years ago

It looks like it's still in the master branch?

mendaxi commented 8 years ago

Also, should I be using git rebase instead of git merge to get updates from mailchuck/master to my own repo? It's a little messy and confusing having the commits that other people have done being relabeled as my own. I'm new to github and git, so apologies if I have caused any inconvenience.