* [ITA] lighttpd @ 2020-10-30 9:04 Glenn Strauss 2020-10-30 13:05 ` Marco Atzeri 0 siblings, 1 reply; 7+ messages in thread From: Glenn Strauss @ 2020-10-30 9:04 UTC (permalink / raw) To: cygwin-apps lighttpd developer (me) would like to adopt the lighttpd package in cygwin. lighttpd 1.4.55 was released in Jan. A request to package was sent to the cygwin list in March. Still no lighttpd 1.4.55 in cygwin. :( I am preparing to release lighttpd-1.4.56, a major release with support for HTTP/2, and figured getting lighttpd-1.4.55 into cygwin would be a good start for a new cygwin package maintainer. lighttpd-1.4.55 has proven to be a stable release. Cheers, Glenn ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-10-30 9:04 [ITA] lighttpd Glenn Strauss @ 2020-10-30 13:05 ` Marco Atzeri 2020-10-30 19:01 ` Brian Inglis 0 siblings, 1 reply; 7+ messages in thread From: Marco Atzeri @ 2020-10-30 13:05 UTC (permalink / raw) To: cygwin-apps On 30.10.2020 10:04, Glenn Strauss wrote: > lighttpd developer (me) would like to adopt the lighttpd package in > cygwin. > > lighttpd 1.4.55 was released in Jan. A request to package was sent to > the cygwin list in March. Still no lighttpd 1.4.55 in cygwin. :( > > I am preparing to release lighttpd-1.4.56, a major release with support > for HTTP/2, and figured getting lighttpd-1.4.55 into cygwin would be a > good start for a new cygwin package maintainer. lighttpd-1.4.55 has > proven to be a stable release. > > Cheers, Glenn > Hi Glenn, can you share the proposed packages somewhere ? Just a formality to verify the package meets the cygwin standards I assume you used the Yaakov's cygport as base. Regards Marco ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-10-30 13:05 ` Marco Atzeri @ 2020-10-30 19:01 ` Brian Inglis 2020-11-01 22:13 ` Glenn Strauss 0 siblings, 1 reply; 7+ messages in thread From: Brian Inglis @ 2020-10-30 19:01 UTC (permalink / raw) To: Cygwin Apps On 2020-10-30 07:05, Marco Atzeri via Cygwin-apps wrote: > On 30.10.2020 10:04, Glenn Strauss wrote: >> lighttpd developer (me) would like to adopt the lighttpd package in >> cygwin. >> >> lighttpd 1.4.55 was released in Jan. A request to package was sent to >> the cygwin list in March. Still no lighttpd 1.4.55 in cygwin. :( >> >> I am preparing to release lighttpd-1.4.56, a major release with support >> for HTTP/2, and figured getting lighttpd-1.4.55 into cygwin would be a >> good start for a new cygwin package maintainer. lighttpd-1.4.55 has >> proven to be a stable release. > can you share the proposed packages somewhere ? > Just a formality to verify the package meets the cygwin standards > I assume you used Yaakov's cygport as base. The previous maintainer cygport is in the Cygwin source package, which you can install using the Cygwin Setup program, or download .../x86{,_64}/release/lighttpd/lighttpd-1.4.54-1-src.tar.xz from any Cygwin mirror, and also in the online repo used by appveyor CI: https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/lighttpd.git Please just copy the contents of your updated lighttpd.cygport and the cygport generated directory hierarchies lighttpd-1.4.55-1.{x86_64,i686}/dist/ onto online shared storage somewhere with access via link(s) posted here. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-10-30 19:01 ` Brian Inglis @ 2020-11-01 22:13 ` Glenn Strauss 2020-11-09 12:46 ` Glenn Strauss 2020-11-22 19:04 ` Achim Gratz 0 siblings, 2 replies; 7+ messages in thread From: Glenn Strauss @ 2020-11-01 22:13 UTC (permalink / raw) To: Cygwin Apps On Fri, Oct 30, 2020 at 01:01:01PM -0600, Brian Inglis wrote: > On 2020-10-30 07:05, Marco Atzeri via Cygwin-apps wrote: > > On 30.10.2020 10:04, Glenn Strauss wrote: > >> lighttpd developer (me) would like to adopt the lighttpd package in > >> cygwin. > >> > >> lighttpd 1.4.55 was released in Jan. A request to package was sent to > >> the cygwin list in March. Still no lighttpd 1.4.55 in cygwin. :( > >> > >> I am preparing to release lighttpd-1.4.56, a major release with support > >> for HTTP/2, and figured getting lighttpd-1.4.55 into cygwin would be a > >> good start for a new cygwin package maintainer. lighttpd-1.4.55 has > >> proven to be a stable release. > > > can you share the proposed packages somewhere ? > > Just a formality to verify the package meets the cygwin standards > > I assume you used Yaakov's cygport as base. > > The previous maintainer cygport is in the Cygwin source package, which you can > install using the Cygwin Setup program, or download > .../x86{,_64}/release/lighttpd/lighttpd-1.4.54-1-src.tar.xz from any Cygwin > mirror, and also in the online repo used by appveyor CI: > https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/lighttpd.git > > Please just copy the contents of your updated lighttpd.cygport and the cygport > generated directory hierarchies lighttpd-1.4.55-1.{x86_64,i686}/dist/ onto > online shared storage somewhere with access via link(s) posted here. lighttpd-1.4.55 package produced by cygport: https://www.gluelogic.com/cygport/lighttpd.patch (patch to lighttpd.cygport) https://www.gluelogic.com/cygport/lighttpd/ (cygport dist/) Future looking for lighttpd-1.4.56: lighttpd is a modular web server. However, the current lighttpd.cygport lumps *everything* together into a single package, with dependencies for all modules. It appears the same was done for nginx. At least Apache httpd.cygport has multiple packages. I plan to do something similar for lighttpd-1.4.56, as lighttpd-1.4.56 adds multiple options for TLS libraries, and a single lighttpd package should not depend on many different TLS libraries available under Cygwin. While lighttpd "could" do so, I would rather not do so for those for whom disk space matters. Question: what is the recommended approach to deploying such a change? The lighttpd base package will still contain all modules for typical usage of lighttpd. However, if an end-user is using mod_openssl and TLS modules are separated into separate packages, then the additional package would need to be installed. On Debian, this transition is occurring by having the Debian lighttpd package "Recommends" lighttpd-mod-openssl, and apt/dpkg will install the openssl module for typical upgrades which accept "Recommends". Is there any similar mechanism on Cygwin? Cheers, Glenn ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-11-01 22:13 ` Glenn Strauss @ 2020-11-09 12:46 ` Glenn Strauss 2020-11-09 19:39 ` Marco Atzeri 2020-11-22 19:04 ` Achim Gratz 1 sibling, 1 reply; 7+ messages in thread From: Glenn Strauss @ 2020-11-09 12:46 UTC (permalink / raw) To: Cygwin Apps On Sun, Nov 01, 2020 at 05:13:37PM -0500, Glenn Strauss wrote: > On Fri, Oct 30, 2020 at 01:01:01PM -0600, Brian Inglis wrote: > > On 2020-10-30 07:05, Marco Atzeri via Cygwin-apps wrote: > > > On 30.10.2020 10:04, Glenn Strauss wrote: > > >> lighttpd developer (me) would like to adopt the lighttpd package in > > >> cygwin. > > >> > > >> lighttpd 1.4.55 was released in Jan. A request to package was sent to > > >> the cygwin list in March. Still no lighttpd 1.4.55 in cygwin. :( > > >> > > >> I am preparing to release lighttpd-1.4.56, a major release with support > > >> for HTTP/2, and figured getting lighttpd-1.4.55 into cygwin would be a > > >> good start for a new cygwin package maintainer. lighttpd-1.4.55 has > > >> proven to be a stable release. > > > > > can you share the proposed packages somewhere ? > > > Just a formality to verify the package meets the cygwin standards > > > I assume you used Yaakov's cygport as base. > > > > The previous maintainer cygport is in the Cygwin source package, which you can > > install using the Cygwin Setup program, or download > > .../x86{,_64}/release/lighttpd/lighttpd-1.4.54-1-src.tar.xz from any Cygwin > > mirror, and also in the online repo used by appveyor CI: > > https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/lighttpd.git > > > > Please just copy the contents of your updated lighttpd.cygport and the cygport > > generated directory hierarchies lighttpd-1.4.55-1.{x86_64,i686}/dist/ onto > > online shared storage somewhere with access via link(s) posted here. > > lighttpd-1.4.55 package produced by cygport: > > https://www.gluelogic.com/cygport/lighttpd.patch > (patch to lighttpd.cygport) > https://www.gluelogic.com/cygport/lighttpd/ > (cygport dist/) > > > Future looking for lighttpd-1.4.56: > > lighttpd is a modular web server. However, the current lighttpd.cygport > lumps *everything* together into a single package, with dependencies for > all modules. It appears the same was done for nginx. At least Apache > httpd.cygport has multiple packages. I plan to do something similar for > lighttpd-1.4.56, as lighttpd-1.4.56 adds multiple options for TLS > libraries, and a single lighttpd package should not depend on many > different TLS libraries available under Cygwin. While lighttpd "could" > do so, I would rather not do so for those for whom disk space matters. > > Question: what is the recommended approach to deploying such a change? > > The lighttpd base package will still contain all modules for typical > usage of lighttpd. However, if an end-user is using mod_openssl and > TLS modules are separated into separate packages, then the additional > package would need to be installed. > > On Debian, this transition is occurring by having the Debian lighttpd > package "Recommends" lighttpd-mod-openssl, and apt/dpkg will install > the openssl module for typical upgrades which accept "Recommends". > > Is there any similar mechanism on Cygwin? > > Cheers, Glenn Re-sending. https://www.gluelogic.com/cygport/lighttpd-1.4.55-1.x86_64/ https://www.gluelogic.com/cygport/lighttpd-1.4.56-1.x86_64/ Cheers, Glenn ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-11-09 12:46 ` Glenn Strauss @ 2020-11-09 19:39 ` Marco Atzeri 0 siblings, 0 replies; 7+ messages in thread From: Marco Atzeri @ 2020-11-09 19:39 UTC (permalink / raw) To: cygwin-apps On 09.11.2020 13:46, Glenn Strauss wrote: > On Sun, Nov 01, 2020 at 05:13:37PM -0500, Glenn Strauss wrote: >> On Fri, Oct 30, 2020 at 01:01:01PM -0600, Brian Inglis wrote: >>> On 2020-10-30 07:05, Marco Atzeri via Cygwin-apps wrote: >>>> On 30.10.2020 10:04, Glenn Strauss wrote: >>>>> lighttpd developer (me) would like to adopt the lighttpd package in >>>>> cygwin. >>>>> > > Re-sending. > > https://www.gluelogic.com/cygport/lighttpd-1.4.55-1.x86_64/ > > https://www.gluelogic.com/cygport/lighttpd-1.4.56-1.x86_64/ > > Cheers, Glenn > GTG see: https://cygwin.com/packaging/key.html#sshkey https://cygwin.com/package-upload.html ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ITA] lighttpd 2020-11-01 22:13 ` Glenn Strauss 2020-11-09 12:46 ` Glenn Strauss @ 2020-11-22 19:04 ` Achim Gratz 1 sibling, 0 replies; 7+ messages in thread From: Achim Gratz @ 2020-11-22 19:04 UTC (permalink / raw) To: cygwin-apps Glenn Strauss writes: > lighttpd is a modular web server. However, the current lighttpd.cygport > lumps *everything* together into a single package, with dependencies for > all modules. It appears the same was done for nginx. At least Apache > httpd.cygport has multiple packages. I plan to do something similar for > lighttpd-1.4.56, as lighttpd-1.4.56 adds multiple options for TLS > libraries, and a single lighttpd package should not depend on many > different TLS libraries available under Cygwin. While lighttpd "could" > do so, I would rather not do so for those for whom disk space matters. > > Question: what is the recommended approach to deploying such a change? You either just strip down the functionality of the previous package to something lean enough but having the typical functionality you think most users will need _or_ you obsolete the previous package and then have a bunch of new packages that do whatever you want. The obsoletion needs to name a suggested replacement. > The lighttpd base package will still contain all modules for typical > usage of lighttpd. However, if an end-user is using mod_openssl and > TLS modules are separated into separate packages, then the additional > package would need to be installed. Keep in mind that setup currently gives no hints on such optional dependencies and when they are needed. > On Debian, this transition is occurring by having the Debian lighttpd > package "Recommends" lighttpd-mod-openssl, and apt/dpkg will install > the openssl module for typical upgrades which accept "Recommends". > > Is there any similar mechanism on Cygwin? No, in part because there is no way for setup to ask the user and use the answer. The libsolv that does the actual package selection could do that, but we don't deliver the inputs. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2020-11-22 19:04 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-10-30 9:04 [ITA] lighttpd Glenn Strauss 2020-10-30 13:05 ` Marco Atzeri 2020-10-30 19:01 ` Brian Inglis 2020-11-01 22:13 ` Glenn Strauss 2020-11-09 12:46 ` Glenn Strauss 2020-11-09 19:39 ` Marco Atzeri 2020-11-22 19:04 ` Achim Gratz
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).