So what's up with this port? Is it ok?
* Alexander Polakov p...@sdf.org [120918 23:10]:
* Stuart Henderson s...@spacehopper.org [120918 21:00]:
Please set SEPARATE_BUILD=Yes for liblinebreak then that's ok with me
to import.
fbreader's still building, but some initial comments on
Works fine on amd64.
On 22:31 Tue 18 Sep , Alexander Polakov wrote:
* Stuart Henderson s...@spacehopper.org [120918 21:00]:
Please set SEPARATE_BUILD=Yes for liblinebreak then that's ok with me
to import.
fbreader's still building, but some initial comments on that:
- looks
This port is based on
http://gitorious.org/openbsd-ports-wip/mainline/trees/300a1b35eb2ba99ddea95715213f16911ee7020f/textproc/fbreader
Description:
FBReader is an e-book reader for various platforms.
FBReader depends on liblinebreak, which is:
Description:
Liblinebreak is an implementation of
On 2012/09/18 20:27, Alexander Polakov wrote:
This port is based on
http://gitorious.org/openbsd-ports-wip/mainline/trees/300a1b35eb2ba99ddea95715213f16911ee7020f/textproc/fbreader
Description:
FBReader is an e-book reader for various platforms.
FBReader depends on liblinebreak, which is:
On 2012/09/18 17:40, Stuart Henderson wrote:
On 2012/09/18 20:27, Alexander Polakov wrote:
This port is based on
http://gitorious.org/openbsd-ports-wip/mainline/trees/300a1b35eb2ba99ddea95715213f16911ee7020f/textproc/fbreader
Description:
FBReader is an e-book reader for various
* Stuart Henderson s...@spacehopper.org [120918 21:00]:
Please set SEPARATE_BUILD=Yes for liblinebreak then that's ok with me
to import.
fbreader's still building, but some initial comments on that:
- looks like it should be SHARED_ONLY=Yes and merge PFRAG.shared
into PLIST.
-
