View Issue Details

IDProjectCategoryView StatusLast Update
0000107Siril[All Projects] Sirilpublic2016-06-15 16:56
Reporterlock42Assigned To 
Status feedbackResolutionopen 
PlatformGNU/Linux 64bitsOSDebianOS VersionTesting
Product Version0.9.1 
Target Version1.0.0Fixed in Version 
Summary0000107: Add and modify files in install process for better integration
DescriptionWe want to open siril by double-clicking on FITS image.
On Linux this is done by installing two files in the correct places.

siril.xml is installed in /usr/share/mime/packages/siril.xml
The point of this file is to associate any file with a .fit, .fits, .fts extension with the "image/fits" mime-type. (maybe other extensions ?)

siril.desktop is installed in /usr/share/applications/siril.desktop
This file does a few things like specifying an icon for Siril, but it also associates the program with the "image/fits" mime-type. This file already exists in the debian package but it must be modified. (for example, icon specified has a bad quality, it should point to another png icon)

Once this is in place the system knows to open Siril when a .fit file (or others) is double clicked and pass the path of the .fit file to Siril as an argument.

Of course OS X achieves this in a different way. Basically an Info.plist file is included in the installer bundle and this file associates files with a .fit, .fits and .fts extension with Siril.

When a user double-clicks on a FITS file, Siril will be started by the system. However, the filename is not passed as an argument as with Linux, instead a FileOpen event must happen which the application needs to handle.
The icon file, siril.icns, must be copied in the correct place in the applications directory structure and then be referenced it in the Info.plist file.
TagsNo tags attached.


related to 0000128 resolvedvinvin Use siril.desktop and others (?) in archlinux 



2016-03-01 01:46

administrator   ~0000227

This is highly dependent on the OS packaging and it's hard to do with autotools. It's probably even discouraged by autotools because it would required hard-coded paths.
How can we manage a different prefix with these files?

I suggest we just reference the files in the SVN for packagers and include them in actual OS packages only. Instructions can still be given in the install doc for people who compile only.

Related Changesets

Siril: trunk r1170

2016-02-17 11:27:32


New linux files for install process (issue 0000107) Affected Issues
add - /trunk/platform-specific
add - /trunk/platform-specific/linux
add - /trunk/platform-specific/linux/siril.desktop
add - /trunk/platform-specific/linux/siril.xml

Siril: trunk r1171

2016-02-17 16:54:18


OS X upload for future dmg file. (issue 0000107) Affected Issues
add - /trunk/platform-specific/os-x
add - /trunk/platform-specific/os-x/Info.plist
add - /trunk/platform-specific/os-x/siril.icns

Issue History

Date Modified Username Field Change
2016-02-17 09:33 lock42 New Issue
2016-02-17 09:34 lock42 Status new => confirmed
2016-02-17 11:27 lock42 Changeset attached => Siril trunk r1170
2016-02-17 11:27 lock42 Summary Add and modify files in installation process for better integration => Add and modify files in install process for better integration
2016-02-17 16:53 lock42 Description Updated View Revisions
2016-02-17 16:54 lock42 Changeset attached => Siril trunk r1171
2016-02-26 16:06 lock42 Assigned To => vinvin
2016-02-26 16:06 lock42 Status confirmed => assigned
2016-03-01 01:46 vinvin Note Added: 0000227
2016-03-01 01:46 vinvin Assigned To vinvin =>
2016-03-01 01:46 vinvin Status assigned => feedback
2016-03-01 10:49 lock42 Target Version 0.9.2 => 0.9.3
2016-04-10 23:52 lock42 Target Version 0.9.3 => 0.9.4
2016-04-18 14:26 vinvin Relationship added related to 0000128
2016-06-15 16:56 lock42 Target Version 0.9.4 => 1.0.0
2016-12-19 16:32 lock42 Category General => Software Development
2016-12-19 16:50 lock42 Category Software Development => Software
2016-12-19 23:30 lock42 Category Software => Siril