Package Details: libevhtp 1.2.10-2

Git Clone URL: https://aur.archlinux.org/libevhtp.git (read-only)
Package Base: libevhtp
Description: A more flexible replacement for libevent's httpd API.
Upstream URL: https://github.com/ellzey/libevhtp
Licenses: BSD
Submitter: aclindsa
Maintainer: aclindsa
Last Packager: aclindsa
Votes: 7
Popularity: 0.000000
First Submitted: 2013-01-19 14:54
Last Updated: 2016-03-03 00:26

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

lianse commented on 2017-04-25 16:15

No, I don't need it. The package I'm interested in (seafile-server) depends on libevhtp-seafile. Just wanted to let you know.

aclindsa commented on 2017-04-22 00:34

@lianse Yes, it appears this project has been abandoned upstream. Because this package is not required by any other packages, I am inclined to delete it.

If anyone thinks it should be kept around, speak up in the next few days and I'll gladly orphan it instead.

lianse commented on 2017-04-20 08:14

Package is broken, upstream Project (and user ellzey) are no longer on github

chrbayer commented on 2016-03-02 18:48

The sha256 sum of the distribution has changed, please check if it is an update or a problem in this package.
Best regards,
Chris

calrama commented on 2015-06-26 09:35

aclindsa: Sorry for the extremely late reply, for some reason I did not receive an Email about this and eventually forgot about this. I have not asked this upstream, since I am migrating away from Archlinux towards Funtoo (there I can use slots&useflags to just have a separate version installed just for seafile based on the same build script).

monochromec commented on 2015-03-25 13:46

Also required by seafile-server.

aclindsa commented on 2015-03-03 12:28

I am not against building a shared library, but -DEVHTP_BUILD_SHARED=ON actually disables the static one, and I don't see a clean way to enable both in the same build. If there were a clean way to do so, I wouldn't mind building both at all.

As a side note, have you tried to ask the developers of seafile why in the world they require SSL to be disabled?

calrama commented on 2015-03-03 12:11

I would argue that at least the building of a shared library should become the default option (so that both static and shared libs are available), but I can see why you wouldn't want to disable ssl as default. I shall upload another package, even though it seems kinda silly with only one option different (How I wish there were slots and use-flags, but I disgress).

aclindsa commented on 2015-02-23 19:00

Hmm... I'm not sure I'm OK with changing the default options here for another project which depends upon it (there is at least one other user of libevhtp in the AUR).

Perhaps if seafile needs libevhtp built a nonstandard way it should provide that library itself (and conflict with this package), or maybe depend upon a new package libevhtp-seafile or something?

calrama commented on 2015-02-23 18:49

Please update the "cmake" invocation to include the options "-DEVHTP_DISABLE_SSL=ON -DEVHTP_BUILD_SHARED=ON", otherwise seafile-server cannot be built[1].

[1] http://manual.seafile.com/build_seafile/server.html#libevhtp

All comments