Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread Erich Titl
Nathan Nathan Angelacos wrote: ... 3. REMOVE the uclibc binaries from webconf.lrp and make EVERYONE choose a library specific plugin? (Probably architecturally correct, but it will be a mess trying to support - "I downloaded webconf.lrp and it doesn't work... You have to download your appropria

[leaf-devel] buildtool not clean enough yet...?

2005-04-07 Thread Paul Traina
Warning:The symlink from /lib/ld-uClibc.so.0 --> /home/pst/LEAF/buildtool/staging/lib/ld-uClibc.so.0 does not exist, this may cause problems with some configure scripts that try to run a compiled program Do we still need this link? If this is the case, then how can buildtool do cross-arch target

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread K.-P. Kirchdörfer
Am Donnerstag, 7. April 2005 20:33 schrieb Mike Noyes: > On Thu, 2005-04-07 at 11:13, K.-P. Kirchdörfer wrote: > > Don't wait for the SF sandbox - I'm waiting for reactivated cron > > for a few month. > > K.-P., > Cron won't help at this time (see SF SR below). All it would do, > since my daily.sh

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread Mike Noyes
On Thu, 2005-04-07 at 11:13, K.-P. KirchdÃrfer wrote: > Don't wait for the SF sandbox - I'm waiting for reactivated cron for a > few month. K.-P., Cron won't help at this time (see SF SR below). All it would do, since my daily.sh script has no error checking, is remove our current exported conten

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread K.-P. Kirchdörfer
Nathan; Am Donnerstag, 7. April 2005 18:54 schrieb Nathan Angelacos: > Thanks Mike, > > Just to make things completely confusing... > > webconf.lrp is a bunch of shell scripts plus 2 programs compiled > for bering-uclibc. So there /is/ a dependency there. This will end up in /bin/packages/ucli

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread Nathan Angelacos
Thanks Mike, Just to make things completely confusing... webconf.lrp is a bunch of shell scripts plus 2 programs compiled for bering-uclibc. So there /is/ a dependency there. However, there are plugins (lwp's) that contain /just/ the 2 binaries. (E.g. Erich Titl's wc207.lwp. It makes webco

[leaf-devel] ANN: UPnP support for Bering-uClibc (repost)

2005-04-07 Thread Paul Traina
Mike asked me to repost this to leaf-devel as well. I'll also introduce myself a bit more. I'm an ex-router software developer (if you're desperately interested, google me) who really doesn't want to spend his retirement working on software routers, but hates the state of the art in consumer grad

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread Mike Noyes
On Thu, 2005-04-07 at 04:55, Nathan Angelacos wrote: > There are two different things in the present webconf cvs repository: > > Source code for the core; and I assume that it could go in config (or stay > under devel/nangel) > > binary lrps & lwps; and for the binary "packaged" versions, K.-P.

Re: [leaf-devel] Repository for webconf plugins

2005-04-07 Thread Nathan Angelacos
Mike, There are two different things in the present webconf cvs repository: Source code for the core; and I assume that it could go in config (or stay under devel/nangel) binary lrps & lwps; and for the binary "packaged" versions, K.-P. makes a good point - the finished packaged stuff should