Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Grégory Hermant" <gregory.hermant@calao-systems.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: add knxweb
Date: Tue, 06 Nov 2012 09:19:33 +0100	[thread overview]
Message-ID: <5098C815.8080901@calao-systems.com> (raw)
In-Reply-To: <20121030135544.6f6d0e40@skate>

Hi thomas,

Le 30/10/2012 13:55, Thomas Petazzoni a ?crit :
> Dear Gregory Hermant,
> 
> On Tue, 30 Oct 2012 13:24:03 +0100, Gregory Hermant wrote:
>> diff --git a/package/knxweb/knxweb.mk b/package/knxweb/knxweb.mk
>> new file mode 100644
>> index 0000000..5ca1760
>> --- /dev/null
>> +++ b/package/knxweb/knxweb.mk
>> @@ -0,0 +1,20 @@
>> +#############################################################
>> +#
>> +# knxweb
>> +#
>> +#############################################################
>> +
>> +KNXWEB_VERSION = 0.6.1
>> +KNXWEB_SOURCE = knxweb-$(KNXWEB_VERSION).tar.gz
>> +KNXWEB_SITE = http://sourceforge.net/projects/linknx/files/knxweb/knxweb-0.6.1/
> 
> The tarball has no license information, this is quite annoying.

How can we manage this kind of package in buildroot ?
> 
>> +define KNXWEB_INSTALL_TARGET_CMDS
>> +	mkdir -p $(TARGET_DIR)/var/www
>> +	cp -rdpf $(@D)/* $(TARGET_DIR)/var/www
>> +endef
>> +
>> +define KNXWEB__UNINSTALL_TARGET_CMDS
>> +	rm -rf $(TARGET_DIR)/var/www/
>> +endef
> 
> Double _ here, so this doesn't work.
> 
> However, how does this web interface works? I see a few PHP scripts,
> but they don't seem to be essential for the operation of the Web
> interface. There's a lot of JS though. Does it communicate with the
> server somehow?
> 
knxweb needs a web server with PHP support.

> I'm surprised that no interpreter like PHP, Lua or Python is needed
> here for the server side, that's why I'm asking.
> 

> Thanks,
> 
> Thomas
> 

gregory

  reply	other threads:[~2012-11-06  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 12:24 [Buildroot] [PATCH] package: add libpthsem Gregory Hermant
2012-10-30 12:24 ` [Buildroot] [PATCH] package: add bcusdk Gregory Hermant
2012-10-30 12:45   ` Thomas Petazzoni
2012-10-30 12:24 ` [Buildroot] [PATCH] package: add linknx Gregory Hermant
2012-10-30 12:48   ` Thomas Petazzoni
2012-10-31  5:01   ` Baruch Siach
2012-10-30 12:24 ` [Buildroot] [PATCH] package: add knxweb Gregory Hermant
2012-10-30 12:55   ` Thomas Petazzoni
2012-11-06  8:19     ` Grégory Hermant [this message]
2012-11-13 20:21       ` Arnout Vandecappelle
2012-10-30 12:42 ` [Buildroot] [PATCH] package: add libpthsem Thomas Petazzoni

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=5098C815.8080901@calao-systems.com \
    --to=gregory.hermant@calao-systems.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox