because they are too lazy to lern how tu buld
packages for their distribution which is at
least for redhat-based distribution trivial
it is no rocket science to take the existing
source package, replace the tarball and after
change some lines in the SPEC-fle rebuild
on the other hand - Ubuntu
On 12/22/2012 09:50 AM, Reindl Harald wrote:
because they are too lazy to lern how tu buld
packages for their distribution which is at
least for redhat-based distribution trivial
Calling people lazy is a bit over the top now isn't it? The reason that
organizations use Red Hat RHEL is, among
Am 22.12.2012 12:16, schrieb Patrick Lists:
On 12/22/2012 09:50 AM, Reindl Harald wrote:
because they are too lazy to lern how tu buld
packages for their distribution which is at
least for redhat-based distribution trivial
Calling people lazy is a bit over the top now isn't it? The reason
Am 22.12.2012 12:16, schrieb Patrick Lists:
On 12/22/2012 09:50 AM, Reindl Harald wrote:
because they are too lazy to lern how tu buld
packages for their distribution which is at
least for redhat-based distribution trivial
Calling people lazy is a bit over the top now isn't it? The reason
Some modern distros (Mageia, Mandriva) use -no-undefined as a default
linker flag for building software. However, undefined symbols are OK if
the binary being linked is a plugin. To detect plugins, build system
looks for presence of -module libtool flag in makefiles.
There are two libraries in
By deafult, CLucene installs the clucene-config.h header
to /usr/lib/CLucene, but fts-lucene tries to include it
from /usr/include/CLucene and fails. Here is how it is fixed in Fedora,
for instance:
sed -i '/DEFAULT_INCLUDES *=/s|$| '$(pkg-config --cflags
libclucene-core)|
