[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#523093: [Bug 364931] Re: [needs-packaging] gnote in karmic



On Sat, May 02, 2009 at 08:08:39AM +0200, Savvas Radevic wrote:
> - 0.3.0 is out :)

I just updated the package in http://people.debian.org/~rmh/gnote/

> - You should have a debian/watch file - I didn't make one since I'm
> based on git. Here's a suggestion:

Added, thanks.

> - I have split the package into 3 different ones: gnote (binary),
> gnote-data (data without compilation), gnote-addins (binary)

This might make sense, but I'm not sure it's a good idea to decide about
package split just yet.

> - I am using boost 1.37 or boost 1.35 or boost - I don't know if
> that's good, but at least it gives more testing control over various
> boost libraries:
>   libboost1.37-dev | libboost1.35-dev | libboost-dev,
>   libboost-filesystem1.37-dev | libboost-filesystem1.35-dev |
> libboost-filesystem-dev,
>   libboost-regex1.37-dev | libboost-regex1.35-dev | libboost-regex-dev,
>   libboost-iostreams1.37-dev | libboost-iostreams1.35-dev |
> libboost-iostreams-dev,
>   libboost-test1.37-dev | libboost-test1.35-dev | libboost-test-dev,

I'll talk to upstream to see which version of boost is preferred.

> - I've also set versioned dependencies, based on autoconf and ./configure:
>   automake (>= 1.9),
>   autoconf (>= 2.53),
>   pkg-config (>= 0.14.0),
>   libgtk2.0-dev (>= 2.14),
>   [...]
>   intltool (>= 0.35),
>   gnome-doc-utils (>= 0.4.2),

Added, thanks.  Except for automake (not needed) and gtk (>= 2.12 is enough
now).

> - For some reason, during document compilation/creation, it requires
> rarian-compat package. I don't know if that's required for Debian, but
> on ubuntu it was spitting errors (maybe the situation changed with
> newer releases).

No idea.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



Reply to: