|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
| * Solve checklib issue http://rerun.lefant.net/checklib/maintainers.P.email@example.com
* Basically, we need to replace the libtool in lyx with Debian's libtool. How this can be done is described [http://people.debian.org/~keybuk/libtool-updating.html here]. I don't know if this should be done on every build or in a patch though. Neither solution seems very satisfying to me.
Subversion repository at Alioth. [http://svn.debian.org/wsvn/pkg-lyx Browse]
[http://packages.qa.debian.org/lyx Package Overview]
[http://bugs.debian.org/src:lyx Bugs], [http://firstname.lastname@example.org with bts-link usertags] (see [:bts-link])
[http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel pkg-lyx-devel mailing list] [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/ Archives]
- Fix bugs in the BTS
- Should we recommend rcs and dvipost or depend on them?
See [http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps the debian policy about dependencies]. Recommends are strong, but not absolute, dependencies. Suggests merely says that a particular package can be used together with this package.
- Send patches upstream. We should aim at having a minimal packaging, as much as possible should be sent upstream. Only Debian-specific and "packaging-specific" stuff should be kept.
01.boost_limits - code seems to be reworked in the boost upstream source. Need to wait until the LyX upstream resyncs with the boost upstream. Alternative: Wait for LyX 1.5 where we can use an external boost lib from Debian. [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2006-June/000898.html Discussion]
Take a look at the manpage error warnings from lintian - [http://lintian.debian.org/reports/mDebian_LyX_Maintainers.html#lyx Lintian check]