All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/lighttpd
Date: Wed, 17 Sep 2008 14:36:21 -0700 (PDT)	[thread overview]
Message-ID: <20080917213621.6F7473C6EF@busybox.net> (raw)

Author: jacmet
Date: 2008-09-17 14:36:21 -0700 (Wed, 17 Sep 2008)
New Revision: 23418

Log:
lighttpd: don't enable openssl support by default

Modified:
   trunk/buildroot/package/lighttpd/Config.in


Changeset:
Modified: trunk/buildroot/package/lighttpd/Config.in
===================================================================
--- trunk/buildroot/package/lighttpd/Config.in	2008-09-17 21:35:51 UTC (rev 23417)
+++ trunk/buildroot/package/lighttpd/Config.in	2008-09-17 21:36:21 UTC (rev 23418)
@@ -8,7 +8,7 @@
 	  Auth, Output-Compression, URL-Rewriting and many more) make
 	  lighttpd the perfect webserver-software for every server that
 	  is suffering load problems.
-		
+
 	  http://www.lighttpd.net/
 
 if BR2_PACKAGE_LIGHTTPD
@@ -16,7 +16,6 @@
 
 config BR2_PACKAGE_LIGHTTPD_OPENSSL
 	bool "lighttpd openssl support"
-	default y
 	depends on BR2_PACKAGE_LIGHTTPD
 	select BR2_PACKAGE_OPENSSL
 	help

             reply	other threads:[~2008-09-17 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 21:36 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-13 10:55 [Buildroot] svn commit: trunk/buildroot/package/lighttpd tpetazzoni at uclibc.org
2008-09-17 21:35 jacmet at uclibc.org
2008-04-24 13:18 ninevoltz at uclibc.org
2007-11-30 12:35 ulf at uclibc.org
2007-09-19 14:02 aldot at uclibc.org
2007-08-11 23:35 ulf at uclibc.org
2007-07-17  0:27 sjhill at uclibc.org
2007-07-15 23:35 ulf at uclibc.org
2007-07-08 18:16 aldot at uclibc.org
2007-07-08 18:14 aldot at uclibc.org
2007-02-11 18:08 aldot at uclibc.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080917213621.6F7473C6EF@busybox.net \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.