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?
- This problem applies to many of LyX's dependencies...
- 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]
- Install MIME info to /usr/lib/mime - Did you think about something like this or more of a xml version like in Ubuntu?
application/x-lyx; lyx-qt %s; nametemplate=%s.lyx; test=test "$DISPLAY" != ""; priority=5 application/x-lyx; lyx-xforms %s; nametemplate=%s.lyx; test=test "$DISPLAY" != ""; priority=4 application/x-lyx; lyx-gtk %s; nametemplate=%s.lyx; test=test "$DISPLAY" != ""; priority=3
Take a look at the manpage error warnings from lintian - [http://lintian.debian.org/reports/mDebian_LyX_Maintainers.html#lyx Lintian check]