Active Topics
-
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 1 day, 5 hrs ago -
Porting apps to Leste (43)
to Maemo 7 / Leste by teroyk - 1 day, 11 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 2 days, 3 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 2 days, 3 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 2 days, 8 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 5 days, 4 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 5 days, 6 hrs ago - more...
|
2010-04-21
, 08:25
|
|
Posts: 318 |
Thanked: 735 times |
Joined on Oct 2009
|
#2
|
You better use the postinst script to modify the permission.
|
|
2010-04-21
, 08:44
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#3
|
From what I've read, debian packages install with the same permissions as when packaged, so try changing the permissions on the file prior to packaging.
 |
|
2010-04-21
, 08:59
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#4
|
Originally Posted by Rob1n
Some permissions get "fixed" during install.
From what I've read, debian packages install with the same permissions as when packaged, so try changing the permissions on the file prior to packaging.
The debian/rules file includes the call to dh_fixperms.
nicolai
|
|
2010-04-21
, 08:59
|
|
Posts: 299 |
Thanked: 241 times |
Joined on Oct 2009
@ Singapore
|
#5
|
Originally Posted by Rob1n
I see. Didn't think that would work as I am on Windows, but maybe I can change permissions in MADDE? I'll try when I get access to my system again.
From what I've read, debian packages install with the same permissions as when packaged, so try changing the permissions on the file prior to packaging.
|
|
2010-04-21
, 10:58
|
|
Posts: 299 |
Thanked: 241 times |
Joined on Oct 2009
@ Singapore
|
#6
|
Originally Posted by b0unc3
Ok, postinst seems to be the way to go...
You better use the postinst script to modify the permission.
Would this be the way to do it?
Code:
#!/bin/sh
# postinst script for qsportsevent
#
# see: dh_installdeb(1)
set -e
# summary of how this script can be called:
# * <postinst> `configure' <most-recently-configured-version>
# * <old-postinst> `abort-upgrade' <new version>
# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
# <new-version>
# * <postinst> `abort-remove'
# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
# <failed-install-package> <version> `removing'
# <conflicting-package> <version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package
case "$1" in
configure) chmod 666 /home/user/qsportsevent.db
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
exit 1
;;
esac
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
#DEBHELPER#
exit 0
|
|
2010-04-21
, 12:51
|
|
Posts: 299 |
Thanked: 241 times |
Joined on Oct 2009
@ Singapore
|
#8
|
Originally Posted by b0unc3
Well... I've now updated my postinst.ex file accordingly, but my .db is still 644. How do I make sure that the file is actually executed? I'm really quite new to this whole packaging stuff...
Use the KISS phylosophy, something like that should do the work:
Code:#!/bin/sh chmod 666 /path/to/file.db exit 0
|
|
2010-04-21
, 12:59
|
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#9
|
On a tangential note I'd say it's not the best to place application resources directly in the user's home directory.
/home/user/qsportsevent.db would be better in, for example, /home/user/.qsportsevent/qsportsevent.db . This reduces clutter and makes it easier to do a good cleanup, without risking other applications, if that's asked for.
/home/user/qsportsevent.db would be better in, for example, /home/user/.qsportsevent/qsportsevent.db . This reduces clutter and makes it easier to do a good cleanup, without risking other applications, if that's asked for.
| The Following User Says Thank You to Joorin For This Useful Post: | ||
|
|
2010-04-21
, 13:01
|
|
Posts: 299 |
Thanked: 241 times |
Joined on Oct 2009
@ Singapore
|
#10
|
Originally Posted by Joorin
Yeah... I sort of knew it was not the best location but did not yet look into where it should be instead. Thanks for the reminder!
On a tangential note I'd say it's not the best to place application resources directly in the user's home directory.
Back to my problem. In the 'sample' postinst.ex file, there is a 'set -e' statement at the beginning of the file. Is that significant? I'll try using it anyway...
I have an app that installs a SQLITE .db file. The .db file is included in my installation package, but on the device it will have permissions set to 644. When I run my app, I hit errors that the database is read only. When I do root + chmod 666 on the .db file, the app will work just fine again. How do I modify the permissions from the outset? I obviously don't want all my users to have to do chmod manually. I even try to change the permissions in code using the Qt setPermissions method, but that didn't to do the work either...
I sort of expect to change something like this:
My Maemo Apps:
QTeachMe - Flashcard app
MobiTifo (which was formerly known as QSportsEvent) - Sports leagues tracking (mainly football).