Re: packaging emel for ubuntu

  • From: Liviu Andronic <landronimirc@xxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Sun, 12 Feb 2012 14:14:55 +0100

Hello Tom
Almost there..


On Sun, Feb 12, 2012 at 2:33 AM,  <tpgww@xxxxxxxxxxx> wrote:
>> As for WITH_POLKIT=1, what build-
>
[..]
> Default command for "run command as root" becomes pkexec
>
Then I have to provide 'policykit-1' at run-time. Now fixed.


I ended up with the following build-time deps:
Build-Depends: libglib2.0-dev, libgtk2.0-dev (>= 2.6), imagemagick,
debhelper (>= 7), quilt (>= 0.46-7~), libmagic-dev, libgtkspell-dev
(>= 2.0.14), udisks, libdbus-glib-1-dev, libacl1-dev

Does anything look strange to you? I'm also hesitating: is 'udisks' a
build-time requirement, or is it only needed at run-time?


As for the run-time deps, here's the resulting list (when built against Lucid):
 Depends: libacl1 (>= 2.2.11-1), libc6 (>= 2.4), libcairo2 (>= 1.2.4),
libdbus-glib-1-2 (>= 0.78), libglib2.0-0 (>= 2.23.5), libgtk2.0-0 (>=
2.20.0), libgtkspell0 (>= 2.0.15), libpango1.0-0 (>= 1.18.0),
libmagic1
 Recommends: libbz2-1.0 | liblzo2-2, grep (>= 2.5.3), sed (>= 4.1.5),
udisks, policykit-1
 Suggests: tracker-utils

Again, does anything seem queer to you? I'm specifically thinking of
'tracker-utils': even though it's not needed at build-time, does emel
still interact with it at run-time? Should I Suggest or Recommend
'tracker-utils' when building with WITH_TRACKER=1?


Last, below are the Makefile.config options that I'm tweaking at build-time:
MAKEOPTS = \
 WITH_KERNELFAM=1 \
 NEW_COMMAND=1 \
 EDITOR_SPELLCHECK=1 \
 WITH_LATEST=1 \
 WITH_THUMBS=1 WITH_THUMBLIB=0 \
 WITH_TRACKER=1 \
 WITH_ACL=1 \
 WITH_POLKIT=1 \
 WITH_UDISKS=1

Are these sensible default for a modern Linux distro? Specifically,
Is WITH_KERNELFAM=1 and USE_INOTIFY=1 the preferred file polling method?
Is WITH_UDISKS=1 preferred over WITH_HAL=1?

Thanks
Liviu


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: