Skip to content
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

Build a Debian package #19

Open
607011 opened this issue Sep 7, 2015 · 9 comments
Open

Build a Debian package #19

607011 opened this issue Sep 7, 2015 · 9 comments

Comments

@607011
Copy link
Owner

607011 commented Sep 7, 2015

No description provided.

@tgamauf
Copy link

tgamauf commented Sep 16, 2015

Ich habe noch nie ein Debian Paket gebaut, aber nachdem ich sowieso vorhabe Qt-SESAME für Ubuntu zu bauen versuch ichs mal!

@607011
Copy link
Owner Author

607011 commented Sep 17, 2015

@eega Great! Thanks and good luck! For a quick start please see my brief guide to compiling Qt-SESAM on Ubuntu in the Wiki.

@tgamauf
Copy link

tgamauf commented Sep 21, 2015

@ola-ct: I have building the package down, but I am still tinkering with icons and storage locations.Furthermore, I am writing a bash script that installs all necessary tools and builds the deb file for x86 and x64 in one go, so everyone can do it! Do you prefer to use the pre-packet source tarball, or the tagged source code directly for this? The difference is that the build script needs either only a version (tag) as input, or a version + tarball.

Another topic I stumbled upon are multi-user systems. I noticed that the makefile installs the binary to /usr/bin, so it is installed for all users. This is ok, but if more than one user uses the computer then the user specific data needs to be handled somehow!
Is this a use case at the moment?

@607011
Copy link
Owner Author

607011 commented Sep 22, 2015

@eega Because releases like 2.0.5 are the best tested versions users should only be able to build packages based on tags.

@607011
Copy link
Owner Author

607011 commented Sep 22, 2015

@eega The settings file is stored in ~/.config (Linux) or in %APPDATA% (Windows) so it's in the user's scope not in the system's.

@tgamauf
Copy link

tgamauf commented Sep 23, 2015

@ola-ct: sorry, I didn't make myself clear - the script checks if a tag exists in both cases! It's only two different ways of obtaining the sources the package is built from:
A. version only

  1. check out tag vX.X.X
  2. build tarball qtsesam_vX.X.X.orig.tar.gz from checked out sources (name required by package
    scripts)
  3. build deb package using tag vX.X.X and tarball qtsesam_vX.X.X.orig.tar.gz

B. version + tarball

  1. check out tag vX.X.X
  2. download vX.X.X.tar.gz
  3. rename vX.X.X.tar.gz to qtsesam_vX.X.X.orig.tar.gz (name required by package scripts)
  4. build deb package using tag vX.X.X and tarball qtsesam_vX.X.X.orig.tar.gz

I prefer A because the user has all the necessary code already downloaded, but if you want me to force the user to use the pre-packed tarball then I will implement approach B.

@607011
Copy link
Owner Author

607011 commented Sep 23, 2015

Acknowledged. A is fine. Thanks in advance.

@ghost
Copy link

ghost commented Aug 14, 2016

Any news on this one?

@maa23
Copy link

maa23 commented Mar 29, 2017

I don't use Debian, but I wrote a build script (called PKGBUILD) for the Arch User Repository (AUR) for Arch Linux. You can find it here: https://aur.archlinux.org/packages/qt-sesam-git/
Maybe it helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants