Re: packaging emel for ubuntu
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Sat, 11 Feb 2012 08:18:47 +1100
On Fri, 10 Feb 2012 19:26:16 +0100
Liviu Andronic <landronimirc@xxxxxxxxx> wrote:
> Hello
> I'm currently working on packaging emel for Ubuntu and sofar it works
> fine [1] but I'd like to get all the dependencies and build options in
> order.
>
> I'm using the following deps at build time:
> Build-Depends: libglib2.0-dev, libgtk2.0-dev (>= 2.6), debhelper (>=
> 7), quilt (>= 0.46-7~), imagemagick, libmagic-dev, libgtkspell-dev
> (>=2.0.14), udisks | devicekit-disks (>= 009), libdbus-glib-1-dev,
> libacl1-dev, libpolkit-gobject-1-dev
>
> Are any optional deps missing? Are there any deps that shouldn't be
> there (I'm specifically thinking of imagemagick, udisks |
> devicekit-disks (>= 009)? Is libpolkit-gobject-1-dev [2] the
> appropriate package for POLKIT=1? I've inspected closely the home
> page, the INSTALL file and the Makefile.config, but I'd like to make
> sure that I'm not overthinking anything.
no 'internal' use of imagemagick, maybe for icon resizing?
udisks for WITH_UDISKS=1
WITH_DEVKIT is deprecated
libdbus-glib-1-dev is needed only for glib < 2.26
libacl1-dev is needed only for WITH_ACL=1
libgtkspell-dev is needed only for EDITOR_SPELLCHECK=1
>
> As for run-time deps, in addition to the above, I also have:
> Recommends: libmagic1, libbz2-1.0 | liblzo2-2 | , file (>= 4), grep
> (>= 2.5.3), sed (>= 4.1.5), xdg-utils, udisks | devicekit-disks (>=
> 009)
file command not used now (libmagic instead)
can't think of any use for xdg-utils
>
> Should any of the above be part of 'Depends' (instaed of
> 'Recommends')? Moreover, I have the following package suggested:
> Suggests: tracker-utils
>
> Is this OK? Are 'tracker-utils' (or anything else related) needed at
> build time?
No.
Several commands used at runtime when WITH_TRACKER=1
>
> Please let me know if I'm getting the deps right. 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:
