Marcus von Appen wrote:
> On, Tue May 01, 2007, Lior Kaplan wrote:
>> I'm packaging ocempgui for Debian .
>> During the build, I've encountered a lot of warning and errors from gcc.
>> Could you review them and send me fixes? (or better, upload an updated
>> version to the website). See the attached files for the log and errors.
> I do not see any errors, just warnings. A lot of them issued by ATK and
> Glib and another bunch of them due to the Python prototypes to conform
> to. The own ones are mostly about the additional unused function
> parameter, so there's no harm from them at all and thus no need to fix
> them. The fix on the other hand would inflict a lot of extra casts
> possibly hiding errors, so I do not will do that.
If that's is fine with you, it's fine with me.
Another issue: I had to apply this patch to setup.py, as the
installation location (and thus install_dir) is different during the
installation than the file location at the target client.
@@ -114,7 +114,7 @@
files = [os.path.join (install_lib.install_dir, "ocempgui",
- adjust_paths (self.install_dir, files)
+ adjust_paths ("/usr", files)
# Update the .pyc file (s).
I install using this:
python setup.py install --root=$(CURDIR)/debian/tmp
and then use the files under $(CURDIR)/debian/tmp to build the debian
package (so that's my root comparing to the client system).
Without the patch above I had Constants.py to contain the path of my
buildroot (e.g. "/tmp/ocempgui-0.2.7/debian/tmp/..."), while the result
should always be relative to the root given.
I guess this is something everyone who builds a package for ocempgui
will encounter, and I'd like to save them the trouble.
C644 D0B3 92F4 8FE4 4662 B541 1558 9445 99E8 1DA0