Hi, I already have a patch that add the following beahviour to viking: - loop over a given list of directory to look for the differents extension files (maps.xml, external_tools.xml, goto_tools.xml). - if $VIKING_CONFIG_PATH is set, it is parsed instead of a built-in list For the moment, I do not load maps*.xml files (next patch?).
Now, it is time for fixing the patch: - which directories to definitively look for? - what exact data should we put in the soonly deployed maps.xml, external_tools.xml, goto_tools.xml? - where to deploy these files? For the directories to look for, I think $(pkgdatadir) as provided by autoconf/automake is the good one. Can someone confirm this option? For "/etc" related I will use @sysconfigdir@. For the data, I plan to ship all example given (we already have an example file) + all maps declared in wiki. Good idea? Too many data? And finally, at the "install" stage, I plan to deploy these data in @pkgdatadir@. I imagine it is the better for packagers. Note that this is the directory used by other Gtk application to ship their .ui files. Please, feel free to comment these choice. Note that before pushing, I will share my patch on this list before, for review. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
