Here Ya go Tres!
If you have questions, let me know
On 08/25/2014 12:09 AM, Tres Finocchiaro wrote:
> @Israel,
>
> Can you please offer this cheat sheet? What you are describing is a
> bit foreign to me, perhaps that would shed some light on it. :)
>
> - tres.finocchi...@gmail.com <mailto:tres.finocchi...@gmail.com>
>
>
> On Mon, Aug 25, 2014 at 12:38 AM, Israel <israeld...@gmail.com
> <mailto:israeld...@gmail.com>> wrote:
>
> On 08/24/2014 10:50 PM, Vesa wrote:
>> On 08/25/2014 06:40 AM, Tres Finocchiaro wrote:
>>> Thanks. Hmmm... intersting... Ok, so you're really just
>>> following our build tutorial to and then running checkinstall.
>>>
>>> This is from the Ubuntu wiki:
>>>
>>> CheckInstall is not designed to produce packages suitable
>>> for distribution. Do not use it to produce packages intended
>>> for the Ubuntu archive or PPAs. Instead, follow the
>>> Packaging Guide.
>>>
>>>
>>> So it seems like it's probably not a good way to do permanent
>>> packaging.
>>
>> Yeah no it isn't. I use checkinstall when I compile stuff from
>> source because it's a neat way to keep track of self-compiled
>> programs, but I don't think it works for creating generic packages.
>>
>> Also a thing to note is that you'll probably also need to pass
>> compiler flags to GCC to generate generic code, otherwise your
>> package will only work for people with similar enough CPU's to yours.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds. Stuff that matters.
>> http://tv.slashdot.org/
>>
>>
>> _______________________________________________
>> LMMS-devel mailing list
>> LMMS-devel@lists.sourceforge.net
>> <mailto:LMMS-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/lmms-devel
> Hi... making a PPA is a better way to do this.
> There are a lot of ways to do this in a better fashion. I already
> have a bzr branch for Utopic with 1.0.3 If you want I could set
> it to build for Trusty and Precise.
> A PPA will work for 32bit and 64bit, however if you want to build
> for PPC or ARM, you will need to build it on one of those
> devices. If you have all the needed Ubuntu build tools you can
> grab the source of the PPA and build the deb from that, and build
> in pbuilder for the specific release you are on, etc..
> A PPA is also better, as the control file automatically pulls in
> all the current depends.
>
> If you want I can give you a pbuilder/bzr cheat sheet I have made.
>
> --
> Regards
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> <mailto:LMMS-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
--
Regards
/*TO GET SET UP TO USE BZR && PBUILDER*/
//install all the things you need
sudo apt-get install gnupg pbuilder ubuntu-dev-tools bzr-builddeb apt-file
packaging-dev
// make your gpg key
gpg --gen-key
//remember your passphrase!!!!
/* now open up ~/.bashrc
* gpg --list-keys
* look at the line from the keyring generateion
* that starts with sec 2048R/######## 2014-01-04
* the # part is your GPGkey
* add the following line, substituting the real
* key for the #
*/
export GPGKEY=########
//i.e. export GPGKEY=259E7E4E
//refresh your bash
source ~/.bashrc
//send the key to ubuntu keyservers
gpg --send-keys --keyserver keyserver.ubuntu.com $GPGKEY
//$GPGKEY works with the line you entered into .bashrc
/* Now for launchpad
* find your fingerprint with:
*/
gpg --fingerprint
https://launchpad.net/~/+editpgpkeys
/*You will get an encrypted e-mail
* thunderbird has an extention to decrypt e-mail...
* however you can save the text from:
-----BEGIN PGP MESSAGE-----
* to
-----END PGP MESSAGE-----
* as a txt file (in this example gpg.txt)
* now run:
*/
gpg --decrypt gpg.txt
//and go to the link.... you are done!!
//make your ssh key
ssh-keygen -t rsa
//choose default filename, enter a password 2x
//open the file, pico doesn't copy the comment on the end... so use gedit
(maybe others)
gedit ~/.ssh/id_rsa.pub
goto https://launchpad.net/~/+editsshkeys
//Configure bzr
//bzr whoami "Name <em...@host.org>
bzr whoami "Doctor Who <thedoc...@lmms.com>"
//bzr launchpad-login lpname
bzr launchpad-login drwho
//configure BASH
gedit ~/.bashrc
//add these lines
//export DEBFULLNAME="Name Comment(optional)"
export DEBFULLNAME="Doctor Who"
//export DEBEMAIL="em...@ghost.org"
export DEBEMAIL="thedoc...@lmms.com"
//restart bash
source ~/.bashrc
//pbuilder-dist <release> create VERY IMPORTANT!!!!!!!!!!!!!!!!
//this makes the chroot environment for whatever release you need
pbuilder-dist trusty create
/***PACKAGE BUILDING***/
/*TO START YOUR BRANCH*/
//cd into the directory you want to be in to do your work i.e. cd
~/programming/bzr
//bzr branch ubuntu:<dist>/<package> <new_directory_name>
//bzr branch lp:ubuntu/lmms is the most current version
//bzr branch lp:<packagename> works with code hosted on launchpad
//i.e. bzr branch lp:tardis
bzr branch ubuntu:utopic/lmms lmms
/*TO MERGE WITH EXISTING SOURCE PACKAGE with --version &number &locationOftar */
//
bzr merge-upstream ../relativePath/to/program.tar.gz
//OR, if the watch file is done right
bzr merge-upstream
//this will automatically download and merge the upstream based on what is in
the watch file.
//then, edit the debian/changelog & commit your changes with:
bzr commit
/*TO TEST YOUR FIX*/
//this command is one I have needed occasionally... but it isn't as good as
below
//bzr builddeb -S --package-merge
//Run this and THEN pbuilder each time you change something to test the fix
bzr builddeb -- -S -us -uc
//cd .. out of the BASE directory to where the dsc file is
//pbuilder-dist <dist> build <package>_<version#>-<ubuntu revision#>.dsc
pbuilder-dist trusty build lmms_1.0.2-0ubuntu1.dsc
//if using bzr merge-upstream lp:lmms
//cd ~/pbuilder/<dist>_result/
cd ~/pbuilder/trusty_result/
//remove any currently installed versions and install newly built version
//be sure to remove any old deb files you may have used...though the newer
version will be the only installed one... sometimes it can cause problems
sudo apt-get autoremove lmms && sudo dpkg -i lmms*.deb
/***COMMITING THE PACKAGE***/
/*TO EDIT CHANGELOG*/
dch -i
//though, personally I like to use a text editor and simply manually edit it.
//i.e. gedit/geany/mousepad/etc...
bzr commit
/*TO PUSH THE CHANGE TO LAUNCHPAD*/
//bzr push lp:/~<user>/ubuntu/<dist>/<package>/<specific package with version #>
bzr push lp:/~israeldahl/ubuntu/trusty/lmms/lmms_1.1.0
//If you are hosting your code on lp it is different
//bzr push lp:<project-name>
bzr push lp:tardis
//or for a sub branch
bzr push lp:tardis/testing
/*HELPFUL COMMANDS*/
//shows status of your branch (i.e. CURRENT)
bzr status
/*** Adding *ANY* file into the /debian directory***/
bzr add
// make a launchpad repo
//This is a command I don't use often.. it makes the +junk branch (IIRC)
bzr init-repo trusty_lmms
//this proposes it for a merger
//which is only useful if you are fixing up an existing program
bzr lp-propose
//this is just so I can copy and paste it as the rules file
//tiny dh rules file
#!/usr/bin/make -f
%:
dh $@
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
