"Hema Seetharamaiah" writes:
> Yes, I provide explicit permission [...]
Thanks. I pushed your patch and related changes to elinks-0.12.
They'll soon get to master too.
> On Sun, May 17, 2009 11:05 pm, Kalle Olavi Niemitalo wrote:
>> - desirable: BSD-like licence, to avoid being forced to
>>
On Sun, May 17, 2009 11:05 pm, Kalle Olavi Niemitalo wrote:
> Can you also give permission to link with OpenSSL?
Yes, I provide explicit permission to link with OpenSSL.
> The FSF apparently recommends also giving explicit permission to
> link with libraries licensed under LGPL:
Yes, I provide
Hema Seetharamaiah writes:
> I license my changes under GPL V2 or later.
>
> Please accept the patch if this is ok.
Can you also give permission to link with OpenSSL? I see your
patch affects only configure.in, which doesn't really become part
of the elinks executable, but anyway I think it'd
Kalle Olavi Niemitalo wrote:
> Your patch also contains spaces between tabs in indentation,
> and a redundant use of EL_SAVE_FLAGS.
>
> I'm attaching a revised patch that should fix these problems.
> I also renamed HAVE_TRE_REGEX_H to CONFIG_TRE because it can
> now be unset even if the header and
"Hema Seetharamaiah" writes:
> Attached is a patch that provides a new option without-tre - which can be
> used to build elinks without libtre dependency.
With that patch, configure without any TRE-related option outputs here:
checking for TRE... checking for TRE in pkg-config... yes
checking f
Hello,
I use elinks-lite in Debian and I noticed that it brings in a libtre
dependency since 0.12-pre3-2 Prior to this the only dependency was
libgnutls.
Attached is a patch that provides a new option without-tre - which can be
used to build elinks without libtre dependency.
Regards,
Hema.>From
