mirror of
https://github.com/shadowsocks/shadowsocks-libev.git
synced 2026-10-26 18:53:41 +00:00
Max LvandClaude Opus 4.6
6423c8e496
Add tests/test_deb_build.sh with four phases: 1. Build .deb packages via dpkg-buildpackage 2. Verify all three packages contain expected files (binaries, man pages, shared library, headers, pkg-config) 3. Install packages and resolve dependencies 4. Smoke-test installed binaries, ldconfig, and headers Add a Linux-only CI step in build.yml to run the test. Statically link the bundled submodule libraries (libcork, libipset, libbloom) into all targets instead of building them as shared libs. These are vendored code built from git submodules, not system libraries, so static linking is correct and eliminates dpkg-shlibdeps warnings about missing .so files. Pass -DWITH_STATIC=OFF in debian/rules since debian build-depends only provide shared library dev packages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
shadowsocks-libev for Debian ---------------------------- The Debian package has added systemd support. A default server service which reads the default configuration in /etc/default/shadowsocks-libev is installed and enabled by default, plus some other service templates placed in /lib/systemd/system, which can be used by users later. The systemd service templates accept one parameter to determine the configuration json file that is used by this instance. For example, if the user starts a service called "shadowsocks-libev-local@foobar.service", This service instance will start the "ss-local" client and read /etc/shadowsocks-libev/foobar.json as its configuration file. -- Boyuan Yang <byang@debian.org> Thu, 08 Sep 2016 19:01:20 +0800