On Thu, 13 Oct 2011 08:12:03 +0200, dtk wrote:
> in my experience, it tends to cause awkward side effects that are hard to
> debug, the main problem being that it overrides all default paths and is
> hard to target at a single problematic application.
I think it's fairly straightforward to prepen
signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20111012/0a0fb503/attachment.pgp>
Hey alip,
On Wed, 12 Oct 2011 18:30:51 +0300, Ali Polatel wrote:
> On Wed, Oct 12, 2011 at 04:55:30PM +0200, dtk wrote:
>>/me dislikes LD_LIBRARY_PATH :/
>
> May I ask why you dislike LD_LIBRARY_PATH?
in my experience, it tends to cause awkward side effects that are hard to
debug, the main pr
From: David Bremner
Currently this builds a native package, but since the source package
is throw away, it should not matter too much, except for the extra
warnings from lintian.
The extra +1 is so that if $(VERSION) is the same as the last released
version (for example outside a git repo) then
From: David Bremner
This makes it less confusing with released Debian versions, now that we have
non-native Debian versions.
---
Makefile.local |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile.local b/Makefile.local
index 38f6c17..2c07bd7 100644
--- a/Makefile.l
Here is a simple way to make debian packages for testing without
fussing about with pristine-tar and so on.
The first patch changes the git snapshot versioning scheme from 0.9-2-g1234
to 0.9+2~g1234 to reduce confusion with released versions like 0.9-2
In principle this should work outside a gi
e happened to know
>a solution.
>/me dislikes LD_LIBRARY_PATH :/
>
May I ask why you dislike LD_LIBRARY_PATH?
-alip
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20111012/b2e18dec/attachment.pgp>
From: David Bremner
Currently this builds a native package, but since the source package
is throw away, it should not matter too much, except for the extra
warnings from lintian.
The extra +1 is so that if $(VERSION) is the same as the last released
version (for example outside a git repo) then
From: David Bremner
This makes it less confusing with released Debian versions, now that we have
non-native Debian versions.
---
Makefile.local |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile.local b/Makefile.local
index 38f6c17..2c07bd7 100644
--- a/Makefile.l
Here is a simple way to make debian packages for testing without
fussing about with pristine-tar and so on.
The first patch changes the git snapshot versioning scheme from 0.9-2-g1234
to 0.9+2~g1234 to reduce confusion with released versions like 0.9-2
In principle this should work outside a gi
Hey guys,
I installed notmuch locally (~/.local) and now the python bindings fail to
find the .so.
Anyone happens to know how to set the rpath in the setup.cfg? Putting it
in the [build] section doesn't work:
~~~snip~~~
$ python setup.py install --prefix=$STOW/notmuch_python
running install
err
On Wed, Oct 12, 2011 at 04:55:30PM +0200, dtk wrote:
Hey guys,
I installed notmuch locally (~/.local) and now the python bindings fail to
find the .so.
Anyone happens to know how to set the rpath in the setup.cfg? Putting it
in the [build] section doesn't work:
~~~snip~~~
$ python setup.py in
Hey guys,
I installed notmuch locally (~/.local) and now the python bindings fail to
find the .so.
Anyone happens to know how to set the rpath in the setup.cfg? Putting it
in the [build] section doesn't work:
~~~snip~~~
$ python setup.py install --prefix=$STOW/notmuch_python
running install
err
13 matches
Mail list logo
