[OpenWrt-Devel] lighttpd-nossl
Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. Best, Christiane ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] New SQLAlchemy Package for Python
New packages for running flexget on Openwrt. found error on previous package. so I am resending file. Signed-off-by: woojae, parknikes...@gmail.com --- Index: feeds/packages/lang/pysqlalchemy/Makefile === --- feeds/packages/lang/pysqlalchemy/Makefile (revision 0) +++ feeds/packages/lang/pysqlalchemy/Makefile (revision 0) @@ -0,0 +1,51 @@ +# +# Copyright (C) 2007-2008 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +include $(TOPDIR)/rules.mk + +PKG_NAME:=SQLAlchemy +PKG_VERSION:=0.7.4 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://pypi.python.org/packages/source/S/SQLAlchemy/ +PKG_MD5SUM:=731dbd55ec9011437a842d781417eae7 +# http://pypi.python.org/packages/source/S/SQLAlchemy/SQLAlchemy-0.7.4.tar.gz#md5=731dbd55ec9011437a842d781417eae7 + +include $(INCLUDE_DIR)/package.mk +$(call include_mk, python-package.mk) + +define Package/pysqlalchemy + SUBMENU:=Python + SECTION:=lang + CATEGORY:=Languages + TITLE:=pysqlalchemy + URL:=http://pypi.python.org/packages/source/S/SQLAlchemy + DEPENDS:=+python-mini +endef + +define Package/pysqlalchemy/description + SQLAlchemy +endef + +define Build/Compile +$(if $(Build/Compile/PyMod),,@echo Python packaging code not found.; false) +$(call Build/Compile/PyMod,., \ +build , \ +BASECFLAGS=$(TARGET_CFLAGS) \ +) +endef + +define Package/pysqlalchemy/install +$(INSTALL_DIR) $(1)$(PYTHON_PKG_DIR) +$(CP) \ +$(PKG_INSTALL_DIR)$(PYTHON_PKG_DIR)/* \ +$(1)$(PYTHON_PKG_DIR) +endef + +$(eval $(call PyPackage,pysqlalchemy)) +$(eval $(call BuildPackage,pysqlalchemy)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] patch to enable building of uuencode applet for busybox
On Sun, 2012-03-18 at 19:57 -0400, i iordanov wrote: Hi Philip, On Sun, Mar 18, 2012 at 5:46 PM, Philip Prindeville philipp_s...@redfish-solutions.com wrote: Why is voicemail encoding using uuencode and not base64??? Well, it can be either. I use uuencode with the -m option which makes it output base64 encoding: -m, --base64use base64 encoding as of RFC1521 If you prefer base64 instead of uuencode, I could alter the script which crafts the email with the voicemail attachment to use base64 and provide a patch to enable the base64 applet to be built by default instead of uuencode. Please advise. If you are willing to adjust the script, can I suggest you convert it to lua. It's not a very large script and you can then use the nixio.bin.b64encode() function. Also you can tidy up the uci access using the lua uci library. http://luci.subsignal.org/api/nixio/modules/nixio.bin.html I thought that the uuencode option on busybox was not exposed, but it is a config variable. There should be some suitable syntax you can use in your package makefile to enable it? I am only familiar with the dependency option, but that is for a whole package. Conor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] patch to enable building of uuencode applet for busybox
On Mon, 2012-03-19 at 10:19 +, Conor O'Gorman wrote: I thought that the uuencode option on busybox was not exposed, but it is a config variable. There should be some suitable syntax you can use in your package makefile to enable it? I am only familiar with the dependency option, but that is for a whole package. That is, of course, no use if you want your package to be installed onto an existing system. Sorry. Conor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
Maybe you are lucky and someone steps up. You are probably better of finding the maintainer (if there's one) directly by looking at the revision log or asking in the openwrt irc channel. The mailing list is often slow in this regard. If it all does not happen in time frame you planned in then you still have the do-it-yourself option. ..ede On 19.03.2012 12:05, Christiane Ruetten wrote: Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
Hi, look at the ctorrent or irssi Makefile. There you can see how to implement the nossl stuff in one Makefile. Regards, Peter On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote: Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
had a look at irssi. does this actually work when both packages are selected? don't you end up with two packages both containing whatever was build first? ..ede On 19.03.2012 13:18, Peter Wagner wrote: Hi, look at the ctorrent or irssi Makefile. There you can see how to implement the nossl stuff in one Makefile. Regards, Peter On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote: Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl
both packaes are build in a sepreate folders so yes - you can select both packages. But you can also building both and testing it ;) /Peter On Monday 19 March 2012 13:24:24 edgar.sol...@web.de wrote: had a look at irssi. does this actually work when both packages are selected? don't you end up with two packages both containing whatever was build first? ..ede On 19.03.2012 13:18, Peter Wagner wrote: Hi, look at the ctorrent or irssi Makefile. There you can see how to implement the nossl stuff in one Makefile. Regards, Peter On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote: Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lighttpd-nossl (+PATCH, RFC)
Hello, My own two cents. I tried to implement it the VARIANT way, and I ended with (basically) repeating everything twice in the Makefile. See attached for details. If someone knows a better way, or if I messed up this patch, I'm ready to listen to criticism. Another way I tried (and I already posted the patches on this list [1]) is to use a CONFIG symbol that lets you choose wether you want to use openssl or not. The changes in the lighttpd Makefile are less invasive and the end result is quite similar (modulo the fact that you cannot build the two versions at the same time). Best regards, -- Emmanuel Deloget [1] http://patchwork.openwrt.org/patch/1924/ Le 19/03/2012 15:05, Peter Wagner a écrit : both packaes are build in a sepreate folders so yes - you can select both packages. But you can also building both and testing it ;) /Peter On Monday 19 March 2012 13:24:24 edgar.sol...@web.de wrote: had a look at irssi. does this actually work when both packages are selected? don't you end up with two packages both containing whatever was build first? ..ede On 19.03.2012 13:18, Peter Wagner wrote: Hi, look at the ctorrent or irssi Makefile. There you can see how to implement the nossl stuff in one Makefile. Regards, Peter On Monday 19 March 2012 12:05:31 Christiane Ruetten wrote: Hi Edgar, just to be explicit: the idea is to have lighttpd-nossl in the official repo so I can get away with distributing a single platform-independent opkg. So I was hoping that the current maintainer could simply add a -nossl build instead of me having to reproduce the complete build effort. What I could do, though, is provide for a package/lighttpd-nossl/ Makefile and company and someone else adds it to the official build system, but chances are that testing my changes, and generally making sure I didn't screw up might surpass the effort that a knowledgable maintainer requires for a copy/modify operation on the current package repo. I might be wrong there, and am grateful for any advice on how to proceed. Cheers, Christiane Am 19.03.12 11:30, schrieb edgar.sol...@web.de: On 19.03.2012 10:52, Christiane Ruetten wrote: Hi, would you be able to easily add a variant of the lighttpd package without the massive libopenssl dependency? It is almost completely filling up the flash in 4 MByte routers, leaving almost no headroom for further functionality, and https is not always required. I am currently in the process of rewriting the PirateBox wifi deaddrop service in an OpenWRT-friendly way. The current target router chosen by the PirateBox community is the TL-MR3020 which unfortunately only has 4 MByte flash. Installing just lighttpd with rewrite and cgi and minimal modules for USB storage takes the system from 1.4M to under 100K of free flash. hi christiane, take a look at the lighttpd makefile https://dev.openwrt.org/browser/packages/net/lighttpd/Makefile how webdav is build in as selectable package. you could do something similar to the currently hard coded openssl support. ..ede Index: packages/net/lighttpd/Makefile === --- packages/net/lighttpd/Makefile (révision 31021) +++ packages/net/lighttpd/Makefile (copie de travail) @@ -9,7 +9,7 @@ PKG_NAME:=lighttpd PKG_VERSION:=1.4.30 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=http://download.lighttpd.net/lighttpd/releases-1.4.x @@ -18,6 +18,8 @@ PKG_FIXUP:=libtool PKG_INSTALL:=1 +PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION) + include $(INCLUDE_DIR)/package.mk define Package/lighttpd/Default @@ -25,186 +27,340 @@ SECTION:=net CATEGORY:=Network URL:=http://www.lighttpd.net/ + TITLE:=A flexible and lightweight web server + MENU:=1 + DEPENDS:=+libpcre +libpthread endef define Package/lighttpd $(call Package/lighttpd/Default) - MENU:=1 - DEPENDS:=+libopenssl +libpcre +libpthread - TITLE:=A flexible and lightweight web server + DEPENDS+=+libopenssl + VARIANT:=ssl endef +define Package/lighttpd-nossl + $(call Package/lighttpd/Default) + TITLE+=(without SSL) + VARIANT:=nossl +endef + +define Package/lighttpd-module/Default + SUBMENU:=Web Servers/Proxies + SECTION:=net + CATEGORY:=Network + URL:=http://www.lighttpd.net/ + DEPENDS:=$(1) +endef + define Package/lighttpd-mod-access - $(call Package/lighttpd/Default) - DEPENDS:=lighttpd + $(call Package/lighttpd-module/Default,lighttpd) TITLE:=Access restrictions module endef define Package/lighttpd-mod-accesslog - $(call Package/lighttpd/Default) - DEPENDS:=lighttpd + $(call Package/lighttpd-module/Default,lighttpd) TITLE:=Access logging module endef define Package/lighttpd-mod-alias - $(call Package/lighttpd/Default) - DEPENDS:=lighttpd + $(call Package/lighttpd-module/Default,lighttpd) TITLE:=Directory alias module endef define Package/lighttpd-mod-auth - $(call
[OpenWrt-Devel] Disk write activity during boot.
How do you track down who is writing to the disk during boot? I'm getting 26KB of writes onto a drive where I don't want any. I'm using ext3 for root on a SD card. Would I be better off making a jffs/squashfs partition for root and then doing my logging onto a separately mounted partition? -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] patch to enable building of uuencode applet for busybox
On Mon, Mar 19, 2012 at 6:19 AM, Conor O'Gorman i...@conorogorman.net wrote: If you are willing to adjust the script, can I suggest you convert it to lua. It's not a very large script and you can then use the nixio.bin.b64encode() function. Also you can tidy up the uci access using the lua uci library. I think it's better if this script remains a shell script, as it calls a bunch of other programs installed on the system to get the job done - it is not really a standalone program. As far as lua is concerned, I could, instead of using uuencode, perhaps write a separate lua script which will do just the base64 encoding for me using the nixio library. http://luci.subsignal.org/api/nixio/modules/nixio.bin.html I thought that the uuencode option on busybox was not exposed, but it is a config variable. There should be some suitable syntax you can use in your package makefile to enable it? I am only familiar with the dependency option, but that is for a whole package. Yes, I also figured the dependency option is for a whole package. Is there a general opposition to enabling either base64 or uuencode in busybox? Won't it be of use to anybody else? I thought I saw somebody on the forum talking about compiling uuencode as a separate package because he needed it. Cheers, Iordan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
