From: Jim Weirich Date: 2004-08-27T22:36:11+09:00 Subject: Re: package glade files Chad Fowler said: > On Fri, 27 Aug 2004 17:01:44 +0900, Roeland Moors > wrote: >> I'm creating a project with ruby/gtk. >> This program uses glade files for the interface. >> What would be the correct place to store these files? >> Should I place these files in lib/ ? >> >> Here is the directory structure RPA suggest: >> http://rpa-base.rubyforge.org/wiki/wiki.cgi?GoodPractices >> But they don't mention glade files. >> >> I'm asking this because I'm creating packages gem/deb. > > Great! > >> Are there gems with glade files as an example? >> > > Not that I know of, but I might be wrong. I'm afraid I don't have > much experience with Glade. Is there somewhere we could download your > code and see how it's laid out? > >> Wouldn't it be nice if rake could make all these packages in one >> step :-) >> > > It _can_ make .tar.gz and gems in one step, but I don't think there's > a debian package task yet. Jim? Hmmm ... no deb packager yet. I've never built a deb package. If you can tell me what's involved (or point me to a web page), I will look into it. The rake supplied package task will handle tar/zip/gem packages currently. Robert Feldt has made some suggestions on making the package task a little more flexible, so it would be a good time to see how other formats could be handled. It would be interesting to know how compatible the GEM metadata spec is with the Debian version. Ideally you want to specify your meta-data only once, so I hope we would be able to construct one out of the other. In the mean time, if you add a deb task by hand, then make the :package task dependent on your .deb file. Then when you do: "rake package", it will automatically build your .deb file along with the tar/zip/gem files. Also tie into the :package_clobber task (I think that's the right name), so that the package is properly cleaned up when done. Regarding your glade files ... are they used at run time or are they just used at build time to construct a GUI? If they are not needed at runtime, then I would keep them out of "lib". Perhaps etc or src directories, depending on whether you view the files as configuration data or source code. If they are needed at run time, then the question is a bit different because the directory they reside in will need to be located at runtime. I would suggest either lib or etc in that case. I hope this helps. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)