Packaging Midori 0.5.6: no devel package any more?

[Kyrill Detinov]

Hello.

I work on packaging Midori 0.5.6.

The build system is changed to use cmake instead of waf¹. And no any
devel files are installed by default except apidocs, enabled by passing
the "-DUSE_APIDOCS=ON" option.

So, what should I do:
1. Drop the -devel package and disable compile APIDOCS.
2. Package apidocs as a separate package (midori-devel-docs?).
3. Something else?


¹ http://www.twotoasts.de/index.php/2013/11/two-webkittens/

[Guido Berhoerster]

Hi,

Post by Kyrill Detinov
I work on packaging Midori 0.5.6.
The build system is changed to use cmake instead of waf¹. And no any
devel files are installed by default except apidocs, enabled by passing
the "-DUSE_APIDOCS=ON" option.
1. Drop the -devel package and disable compile APIDOCS.
2. Package apidocs as a separate package (midori-devel-docs?).
3. Something else?…
¹ http://www.twotoasts.de/index.php/2013/11/two-webkittens/

the question is whether this is an intentional change or a bug
introduced by the cmake switch. I would gess the latter since there is
no changelog entry about this and it doesn't make sense to offer API
docs if external plugins are not supported any more.

So I'd just mail upstream and ask and then decide whether to drop
the devel package or to install the headers manually in the specfile
until upstream fixes the issue.

[Guido Berhoerster]

Post by Guido Berhoerster
Hi,

Post by Kyrill Detinov
I work on packaging Midori 0.5.6.
The build system is changed to use cmake instead of waf¹. And no any
devel files are installed by default except apidocs, enabled by passing
the "-DUSE_APIDOCS=ON" option.
1. Drop the -devel package and disable compile APIDOCS.
2. Package apidocs as a separate package (midori-devel-docs?).
3. Something else?…
¹ http://www.twotoasts.de/index.php/2013/11/two-webkittens/

the question is whether this is an intentional change or a bug
introduced by the cmake switch. I would gess the latter since there is
no changelog entry about this and it doesn't make sense to offer API
docs if external plugins are not supported any more.
So I'd just mail upstream and ask and then decide whether to drop

Thinking about it, it should be fine to directly report a bug.

Post by Guido Berhoerster
the devel package or to install the headers manually in the specfile
until upstream fixes the issue.

And if you need help with that let me know (private mail is fine).