On Tue, 2008-03-25 at 18:23 +0100, Guido Diepen wrote: > Hi, > > > > > For the base config, I installed config.xml in site-packages/SyncEngine, > > dropped the third of the above lines so self.sepath refers to this dir, > > and further on changed config/config.xml to just config.xml. I did this > > because it seemed inappropriate to have a file called config.xml in > > site-packages. > > > > I think it would still be better in /usr/share/sync-engine or something. > > But everything that is under the site-packages directory is perfectly > accessable from within the python script. You can figure out the location of > your module and then get the right path for your config.xml file. > > If you create it in /usr/share/sync-engine, you have the probem of accessing > it in your code (without hardcoding, because what if the program was > installed with different prefix the /usr ). > > I have had the same problem when I was figuring out where to put the data > files of synce-kpm. The problem is that I don't know of any way that you can > change locations (i.e. update prefixes) of your python files from within the > setup.py. > > Guido Diepen >
Not being very good at python I won't comment about how to do it :) But I agree, if it did go somewhere outside the python tree it should be left to packagers to patch it for the distro. In my deb I can happily hardcode a path because that is where it is in that distro. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
