Yes, I did and I followed the new standard by using git submodules.
Packaging is somewhat different from the previous version in a sense that
it adds static library in devel package. This would allow developers to
choose whether to link statically or dynamically in response to the current
On Tue, Mar 6, 2018 at 3:41 PM, Pekka Vuorela <pekka.vuor...@jolla.com>
> On Tue, 2018-02-27 at 15:35 +0200, rinigus wrote:
> > For those who are interested in up-to-date hunspell, I have packaged
> > it under https://github.com/rinigus/pkg-hunspell with the builds
> > available at https://build.merproject.org/package/show/home:rinigus:k
> > eyboard/hunspell .
> > Packaging script is based on https://git.merproject.org/mer-core/huns
> > pell with the further split of development and tools packages for
> > hunspell. That allows to get hunspell as a static library and build
> > against it.
> > I wonder whether anyone has packaged more recent version of
> > > hunspell than the one available at https://git.merproject.org/mer-c
> > > ore/hunspell and on our devices?
> > >
> > > Also, it looks like mer repo contains source dump of hunspell. If I
> > > remember other repos correctly, it seems to be the way for other
> > > packages as well. Any reasons for preferring such model instead of
> > > git submodules? Looks to be more difficult to update it to the
> > > current version.
> Looks like you made a PR for the update. Nice, we'll look into that.
> For the record, some older packages are having source code dumps. Those
> have been gradually migrated for git submodule setup for easier
> maintenance and usage.
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe@lists.
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org