Debian packaging

[ghost]

No description provided.

[Lasall]

Please consider using newest version 9.

[Lasall]

Please perform a lintian check (with latest lintian) to make sure package has no common packaging issues.

[p-e-w]

@Fuzzgun: Thank you very much for your contribution. Being a complete stranger to packaging, I'll probably need some time to try this out myself, but I definitely intend to merge if there are no grave issues.

Will this generate a .deb that is compatible with Ubuntu also? Are you a Debian/Ubuntu maintainer with upload access?

[Lasall]

Again the compiler dependency should be (for saucy e.g.): valac-0.18 | valac-0.20

[Lasall]

@p-e-w : This package will only compile on Ubuntu because of the libunity dependency. I myself wanted to (and will) file an ITP bug (intention to package) for Debian (and propose a package to the archive) as soon the project will become more stable.

[p-e-w]

I see. Maybe a PPA for Ubuntu would also make sense, I hear that Launchpad supports automatic daily builds from GitHub...

[p-e-w]

BTW libunity is an optional dependency for Final Term. Maybe it could be made into an optional dependency for the build script also.

[ghost]

Yes. Running the debian.sh script will generate a deb file suitable for Ubuntu. Sadly I'm not a Debian or Ubuntu maintainer, but I can create a PPA which will make installation easy on Ubuntu.

Having working deb files is probably the best way to get software out to the biggest percentage of Linux users. Although it looks like this project is still at an early stage I think it has potential (pending bug fixes and multi-window capability) to become the standard terminal application on many distros.

[p-e-w]

Where are such unstable development .deb files best hosted?

[p-e-w]

@Fuzzgun: You are absolutely right, we're still in the early stages here. I estimate it will take at least another 3 months until usable functionality and stability is reached.

[ghost]

If you have a Launchpad account then you can create your own PPAs. I have some instructions on uploading to PPAs here http://robotics.uk.to/wiki/How_to_create_an_Ubuntu_PPA

[p-e-w]

I don't have a LP account yet but of course I can create one. This week I intend to spend my Final Term dev time exclusively on infrastructure and stabilizing, but afterwards I'm going to look into the PPA thing. If you already know how to make a daily build PPA linked to GitHub and feel like doing it yourself, I won't stop you, though... :)

[ghost]

I'll maybe have a go at that, since it is possible to link a Launchpad project to Github.

@Lasall There are some remaining Lintian warnings still to be fixed.

[ghost]

On notifications and the messaging menu in Ubuntu Unity I know that this has changed since 12.10 and all the documentation available about those things on the Ubuntu web site is out of date. A bug was recently created for that, but at present the current Unity API remains either undocumented or poorly/misleadingly documented.

https://bugs.launchpad.net/ubuntudeveloperportal/+bug/1178700

[Lasall]

A really cool thing would be to get the version string from git tags. (But that's rather advanced, an example can be found in vala sourcecode: build-aux/git-version-gen)

[ghost]

Yes, that would save some manual effort when increasing the version number.

[p-e-w]

I'm not using any tags ATM because I'm not actually versioning yet. I consider Final Term to be in an unstable, pre-alpha state where everything can change at any time and I do not want to worry about semantic implications of version numbers at the moment.

Once basic, everyday functionality is ready, versioning will start and I'll switch from a "push at will" model to an actual release cycle.

At that point, pulling the version from tags would indeed be very cool :)

[p-e-w]

Just tested your master branch on Ubuntu and it compiled the package with no problems. Installation from the .deb also worked. Wonderful :)

Will examine this in more detail later and then merge (please get rid of the binary manpage archive first though; the archive should be generated on build). I hope it's alright for you if I squash the ~20 commits into one.

Also, could you kindly rebase on top of the current master?

[versable]

After backporting keybinder-3.0, I managed to package finalterm for elementaryOS luna beta 2 (based on Ubuntu 12.04). If you want I could start a final term project on lp, linked to your git repo, with a debian build branch, it should built fine. I could also open a daily PPA, with the vala PPA as dependancy. I plan to include finalterm on the elementary community PPA.

[versable]

Also, could you please update the Categories line in your .desktop file on your git branch to:

Categories=GTK;Utility;TerminalEmulator;System;

[versable]

Just looked at fuzzguns debian commit, pretty similar to mine. I wouldn't merge the commit, i would rather create a debian-build branch, and create a lp recipe with nested branches.

[p-e-w]

@versable: That sounds great. I'd really appreciate if a PPA was available but at the moment I am lacking the time to maintain it myself. So go right ahead! :)

Maybe you can still find something useful in fuzzgun's work, though. It went through a lot of iterations; unfortunately, I haven't heard from him in a while now.

[p-e-w]

Categories updated: 911944b

[versable]

I'll use fuzzguns debian commit since it is more complete than mine. Maybe I will have a daily PPA up and running tomorrow with Ubuntu 12.04 - 13.10 support.

[ghost]

If you need a PPA I can create one. I could also have a go at using Open Build Service to create install for multiple distros.

[versable]

fuzzgun: How about combining forces?

[versable]

Project page is up on LP:
https://launchpad.net/finalterm

The main branch lp:finalterm syncs with your git branch every 5 hours:
https://code.launchpad.net/~versable/finalterm/finalterm

Here is a testing PPA which takes your synced branch, nests it with my deb-packaging branch and attempts to build:
https://code.launchpad.net/~versable/+archive/finalterm-daily

Everytime you update your git branch a new deb will be build and put into the PPA.
The PPA has also the vala-team ppa as dep (meaning it pulls the updated vala files when it attempts to build)

Let's see if it builds ;)

[versable]

Failed to build:
https://launchpadlibrarian.net/142048178/buildlog_ubuntu-saucy-amd64.finalterm_0.1-0~40~saucy1_FAILEDTOBUILD.txt.gz

x expand issue from bug #38

[versable]

Fixed,

build fine after I fiddled around with the control file:
https://code.launchpad.net/~versable/+archive/testing-ppa/+packages

I resettet the daily PPA, LP should build for it fine in a couple of hours

[p-e-w]

(On a brand new Raring system ...)

sudo add-apt-repository ppa:versable/finalterm-daily
sudo apt-get update
sudo apt-get install finalterm
finalterm

Done!

This is awesome :)))))))) Thank you!

I'm a bit short on time ATM, but I'll wrap this up as soon as I can, add this to the installation instructions and blog about it. This PPA makes Ubuntu by far the easiest platform to install Final Term on.

[versable]

Then you'll be glad to hear that after backporting keybinder-3.0, and pulling in backports from clutter, atk and cogl, I have managed to get an Ubuntu 12.04 built. After all, Final Term should support the Ubuntu 12.04 LTS release ;).

[p-e-w]

For the credits: The branch http://bazaar.launchpad.net/~versable/finalterm/deb-packaging/files/head:/debian/ looks like @Fuzzgun's original pull request (with the exception of the manpage stuff). Is it OK for you both if I give you shared credit for the creation of the PPA?

[versable]

Give @Fuzzgun full credit for the debian branch. I just pulled everything together and fought with LP ;)

[versable]

It works fine on Ubuntu 12.04, just tested it on a fresh install in Virtualbox

[versable]

I have created a team page on Launchpad for Final Term, and made a PPA for it, as I don't want to impose my name.

Final Term will built for it in a couple of hours, then that PPA should be ready.

You shouldn't use mine as the new PPA has a more appropriate name, as in:

ppa:finalterm/daily

[p-e-w]

PPA added to installation instructions: 4793545

[dol]

Thx for the package definition.