On Sat, 2011-06-25 at 16:44 +0100, Nelson Marques wrote: 
> Hi all,
> 
> I've just submitted 'synapse'[1] to G:Apps. This package has all the
> plugins enabled except for two optional:

[1] was forgotten in the appendix I'm afraid. so no reference to the
actual app (and google lists a lot of hits for synapse)

Anyway, The correct link would be http://launchpad.net/synapse-project
(as found in your .spec file).

As for the packaging, there is only a small mumbo jumbo as you're
already used to receive from us I'm afraid. Nothing big actually,
the .spec looks clean and sane.

some missing parts:
As you install a .desktop file, you should call
  - %desktop_database_post in %post
  - %desktop_database_postun in %postun

And the rest is really only minro nit-picking from our side :)

> * AppIndicator (we don't use it do we?);
That probably depends on how far you want to push it. Optionally, of
course, we can have the build flag controlled by the PrjConf as we have
for others already. Then you can link the package to your prj and have
the appindicator built too.

> * rest-0.6 (I'm not really sure what this is, but it's flagged as
> optional and we don't have the dependency on Factory);

right. 0.7 is outdated and we have 0.7 in GNOME:Apps and Factory (pkg
librest)

>From the package description:
This library was designed to make it easier to access web services that
claim to be "RESTful". A reasonable description is that a RESTful
service should have urls that represent remote objects, which methods
can then be called on.

It is comprised of two parts:

    * the first aims to make it easier to make requests by providing a
      wrapper around libsoup.
    * the second aids with XML parsing by wrapping libxml2.

> This package hasn't yet been ported to GTK3, but I'm on it. I think
> everything is cool on the package.
> SR:  74510

Do we have an approximate timeline for GTK3 port? Anyway, this should
not really matter. I foresee that we'll be carrying and maintaining GTK2
for a good while.

Dominique

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to