[00:00] <[mbm]> there's a matrixssl version of stunnel on the forum and someone wrote an even smaller axtls stunnel package
[00:00] <{Nico}> we have a matrixtunnel package but not tested afaik
[00:00] <[mbm]> I think that we should block http access my default
[00:00] <[mbm]> er by default
[00:01] <[mbm]> as is our security is pretty weak
[00:01] <[mbm]> moving webif to https will mean that your two methods of access (ssh, https) are encrypted
[00:02] <[mbm]> which should be reasonably secure for now
[00:03] <groz> i'd hedge toward allow http on an intial flash, then let folks disable it
[00:03] <groz> it'll generate a LOT less 'what happened' questions
[00:03] <[mbm]> groz: what if we just did a bounce and had http redirect to https?
[00:03] <{Nico}> [mbm]: what's that axtls stunnel package?
[00:04] <groz> I'm just thinking of reducing the amount of dumb problems
[00:04] <groz> that clueless folks will bump into
[00:05] <[mbm]> {Nico}: it was mentioned somewhere .. I'll have to find it agian
[00:05] <[mbm]> basically axtls is an even smaller ssl then matrixssl
[00:07] <[mbm]> ...
[00:07] <[mbm]> there will be a 1.0-preview released soon just to show people what we've been working on with buildroot-ng
[00:07] <[mbm]> which will mark the first time that we've ever posted binaries of anything but whiterussian
[00:08] <[mbm]> so I expect that to generate tons of interest
[00:08] <groz> is the plan to do more than wrt arch for that preview ?
[00:08] <[mbm]> since most people haven't seen that stuff before
[00:09] <[mbm]> groz: yeah, I'd really like to do as many archs as reasonably stable so we'll also have x86 and uml in there
[00:09] <groz> ok, here's one thought
[00:09] <groz> if we have a bit of a demo on how to work with packages in uml
[00:09] <groz> so it's trivial easy, no need to flash routers
[00:09] <groz> it'll geenrate a lot of developer interest
[00:09] <[mbm]> well, that gets into the next bit of agenda
[00:10] <groz> but the real question first
[00:10] <groz> who is the 'target market' for that ?
[00:10] <groz> users, developers, clueless ?
[00:10] <[mbm]> I'm also looking for someone to be 'editor' of the openwrt.org front page
[00:10] <[mbm]> and get some new content up so it's not the same 2 posts from 6 months ago
[00:10] <groz> I'm in the final throws of a product release cycle here today, if the rest of th eday goes on track
[00:11] <groz> then i'll be deep into the x86 stuff by tomorrow
[00:11] <[mbm]> I'd really like the openwrt.org front page to be more of a development blog with comments by various developers on what they're working on
[00:11] <[mbm]> and some nice articles on how the system works
[00:12] <[mbm]> I've already got a few I've written up
[00:12] <groz> well, the way buildroot-ng goes together
[00:12] <groz> i think if a lot of folks doing thier own thing on embedded stuff see it, and try it
[00:12] <malbon> I can write an article on a few things I am working on. I'll make a start.
[00:12] <groz> we will see a flood of folks jump in
[00:12] <[mbm]> I'm also thinkonf of adding some dynamic content to the front page
[00:13] <[mbm]> we really have a problem right now where it's hard to see that openwrt has actually done anything
[00:13] <groz> hehe, that's gonna change i think
[00:13] <groz> when folks start working with -ng
[00:13] <[mbm]> front page is the same as it's been for months
[00:14] <[mbm]> there's some discussion on the forum but mostly just end user troubles
[00:14] <groz> something that would also be kinda cool
[00:14] <groz> along the lines of what debian does
[00:14] <[mbm]> the release (rc5) is months old
[00:14] <[mbm]> ..
[00:14] <groz> database of packages that have been imported into ng, along with thier functional status for various archs
[00:14] <[mbm]> so I want to add some trac stats to the front page so when you look at it you can see 'ah! something has been done'
[00:15] <groz> we've got a lot in now, but, i'm sure most have only been built, and not really tested, on only one arch
[00:15] <[mbm]> oh, you've reminded me of something else -
[00:15] <[mbm]> I also want to bring back the tracker .. not to keep track of external repos (as it was originally written)
[00:15] <[mbm]> but more of a search engine for the packages that we maintain
[00:16] <[mbm]> debian and ubuntu have a similar online package system
[00:16] <[mbm]> basically this - http://packages.ubuntulinux.org/dapper/x11/xserver-xorg-driver-s3
[00:16] <groz> rite
[00:17] <groz> but, it's a fair amount of work i suspect
[00:17] <[mbm]> not really
[00:17] <groz> or is there a way to create that with trac ?
[00:18] <[mbm]> we should be able to recycle most of that from the old package tracker we used to have
[00:18] <{Nico}> oh, my baby...
[00:18] <Kaloz> :P
[00:19] <[mbm]> {Nico}: think it'd be hard to get the package tracker to spit out pages like that?
[00:19] <[mbm]> should be this: description, dependancies, files includes in the package
[00:19] <[mbm]> with the deps hyperlinked
[00:20] <{Nico}> deps were already
[00:20] <[mbm]> as was the description
[00:20] <{Nico}> we should add arch
[00:21] <[mbm]> yep
[00:21] <{Nico}> package content implies some package retrieval/extraction
[00:22] <[mbm]> hmm right .. all the rest of the info is just parsing the package file
[00:23] <{Nico}> why not add the tracker source to trac?
[00:23] <[mbm]> something else we could do if we're keeping track of package contents - create a folder representing the root directory after every package has been installed
[00:24] <[mbm]> and you can surf around and click on any file in there
[00:24] <[mbm]> and it will tell you what packages install that file
[00:25] <{Nico}> you mean the online imagebuilder we talked about, linked to ther tracker?
[00:25] <[mbm]> not quite
[00:25] <groz> have you ever used rom-o-matic ?
[00:25] <malbon> etherboot's rom-o-matic?
[00:25] <groz> yes
[00:26] <[mbm]> {Nico}: this is more of a reverse package lookup
[00:26] <malbon> that's pretty nifty.
[00:26] <groz> yah, but an online image builder
[00:26] <groz> that just stuffs packages into a blank image
[00:26] <groz> then lets you dl that
[00:26] <groz> very slick
[00:26] <groz> and an absolute bandwidth pig
[00:26] <[mbm]> {Nico}: normal lookup ytou click a package and you get a list of the files in the package, in this case you'd click a file and get the list of packages that create that file
[00:27] <{Nico}> [mbm]: ok
[00:27] <[mbm]> {Nico}: so you might see an apache directory browser showing /etc, you click on inittab and it tells you that inittab is installed by base-files
[00:28] <[mbm]> groz: yeha, we've talked about turning image builder into an online version like rom-o-matic .. we just haven't actually done it yet
[00:29] <{Nico}> [mbm]: i was thinking to an image browser
[00:29] <[mbm]> ?
[00:30] <{Nico}> show the content of an image like you mentionned
[00:30] <malbon> sorry folks, I've got to go. see-ya all.
[00:31] <[mbm]> {Nico}: ah, I don't think of what I just said as an image browser
[00:32] <{Nico}> we would just have to generate a .content file (with find) for every image and use that file with the image browser
[00:33] <{Nico}> i used to put a .content for every packages in the backports directory
[00:33] <{Nico}> that might be used for package content with the tracker
[00:33] <[mbm]> well we already generate a packages.filelist
[00:35] <{Nico}> i admit i'll prefer a plain old tar listing
[00:36] <[mbm]> well, I mean the repository, there's Packages and Packages.filelist
[00:36] <[mbm]> and parsing those two files tells you everything you need to know about all files in that repository
[00:39] <{Nico}> right
[00:40] <[mbm]> hmm .. think that covers all the agenda for this meeting
[00:40] <[mbm]> anyone else have anything to add?
[00:40] <groz> you think ?
[00:40] <[mbm]> groz: on very rare occasions
[00:41] <groz> does it hurt ?
[00:41] <[mbm]> I try not to think about that
[00:41] <groz> lol
[00:43] <[mbm]> so.. recap .. rc6: webif cleaup, testing .. 1.0-preview soon after .. new content for the front page (hire an editor?)
[00:43] <groz> hire ??
[00:43] <[mbm]> well, in the open source sense
[00:43] <groz> one thing that could work well, is, the changelog brought to the front page
[00:44] <groz> possbibly a summary of the last few commits
[00:44] <[mbm]> yeah, that's one of those useless dynamic widgets I talked about
[00:44] <groz> the great thing about dynamic widgets
[00:44] <[mbm]> basically just there to make it look like something has happened since the last time you visited the page
[00:44] <groz> once they are in, you dont have to fusss to get fresh content
[00:44] <[mbm]> serves no other purpose
[00:45] <groz> it serves the purpose of 'fresh stuff' with 'no extra effort'
[00:46] <[mbm]> right
[00:46] <groz> but that gets back to my question earler
[00:46] <[mbm]> still want to get some actual content up though
[00:46] <groz> define the target audience for the ng preview
[00:46] <{Nico}> fresh and but a bit boring maybe
[00:46] <groz> develpers, users, or clueless ?
[00:46] <[mbm]> like I said I want to make the front page into a development blog of sorts
[00:47] <[mbm]> with articles and such
[00:47] <[mbm]> groz: if it works it'll attract tons of new developers, if it fails we get tons of users asking us why google.com doesn't load
[00:47] <groz> LOL
[00:47] <groz> yah, well
[00:48] <groz> i'm thinking most of the interest will be arches other than wrt
[00:48] <[mbm]> right
[00:48] <[mbm]> the wrt arch is dead
[00:48] <groz> i dunno about that
[00:48] <[mbm]> and that's why I want to kill off the whiterussian branch and move on
[00:48] <groz> but it's well supported
[00:48] <groz> well, if you actually want to use it for real today, you gotta use wr
[00:48] <groz> cuz google doesn't load
[00:49] <[mbm]> well, the number of vendors still making hardware from the whiterussian era is quickly dropping
[00:50] <groz> I have confirmation from my sources that the GL will still be available till the new year
[00:50] <groz> now, how reliable are they, dunno
[00:50] <groz> but they have never steered me wrong before
[00:50] <[mbm]> and there seems to be less and less interest in actually doing anything new and exciting with the wrts
[00:51] <groz> well, i can understand why you lost interest in it
[00:51] <[mbm]> so all we really see is end user issues
[00:51] <groz> there's still a bunch of folks actually using the things
[00:51] <[mbm]> using yes, developing? no
[00:52] <[mbm]> so to answer your question the 1.0 preview isn't something for end users to run on a daily basis, it's really something to show developers how great the ng branch is
[00:53] <[mbm]> and the highly unlikely event that it causes some slashdot interest
[00:53] <groz> it shouldn't have any problem doing that
[00:53] <groz> it basically makes the original buildroot env obsolete
[00:53] <groz> and there's still a lot of folks workjing with buildroot variants
[00:54] <[mbm]> we already made the original firmware obsolete long ago
[00:54] <groz> that will switch in a heartbeat when they see it
[00:55] <[mbm]> as kaloz described it, it's really a "call for package maintainers"
[00:55] <groz> rite
[00:56] <groz> so the goal should be, to make it as easy as possible for folks to 'cmon in and play'
[01:05] <CIA-17> nico * r4546 /packages/net/squid/Makefile: add prereq-check on openssl devel lib to squid, standardize, indent
[01:14] <{Nico}> we already have libraries in packages/libs that don't build packages (like pwlib and openh323)
[01:14] <{Nico}> any objections moving toolchain/libnotimpl to packages/libs?
[01:16] <{Nico}> malbon: ping
[01:16] Action: {Nico} forgot, malbon is already gone
[01:47] <db90h> i am excited about the upcoming releases of openwrt
[01:47] <[mbm]> :)
[01:47] <db90h> i think am finally understanding why i have been so wrong in trying to encourage openwrt to target end users..
[01:48] <db90h> openwrt is (or will be) the definitive base for almost any embedded linux platform
[01:48] <[mbm]> that's the plan
[01:58] <CIA-17> nico * r4547 /packages/libs/axtls/ (Makefile files/config): update axtls to v1.01
[02:36] <CIA-17> nico * r4548 /packages/libs/axtls/Makefile: axtls is now on sourceforge, change urls
[16:45] <common> nbd: SYN?
[16:57] <nbd> common: SYN/ACK
[17:02] <common> gave the openrg bootloader a shot?
[17:02] <nbd> not yet
[17:03] <common> ping me if you do, i'll test it
[17:12] <nbd> k
[23:13] <CIA-17> florian * r4549 /packages/net/elinks/Makefile: Restore plain old configure script
[23:35] <CIA-17> florian * r4550 /packages/utils/wx200d/ (. Config.in Makefile ipkg/): Port wx200d to -ng
[00:00] --- Thu Aug 10 2006
[00:00] <{Nico}> we have a matrixtunnel package but not tested afaik
[00:00] <[mbm]> I think that we should block http access my default
[00:00] <[mbm]> er by default
[00:01] <[mbm]> as is our security is pretty weak
[00:01] <[mbm]> moving webif to https will mean that your two methods of access (ssh, https) are encrypted
[00:02] <[mbm]> which should be reasonably secure for now
[00:03] <groz> i'd hedge toward allow http on an intial flash, then let folks disable it
[00:03] <groz> it'll generate a LOT less 'what happened' questions
[00:03] <[mbm]> groz: what if we just did a bounce and had http redirect to https?
[00:03] <{Nico}> [mbm]: what's that axtls stunnel package?
[00:04] <groz> I'm just thinking of reducing the amount of dumb problems
[00:04] <groz> that clueless folks will bump into
[00:05] <[mbm]> {Nico}: it was mentioned somewhere .. I'll have to find it agian
[00:05] <[mbm]> basically axtls is an even smaller ssl then matrixssl
[00:07] <[mbm]> ...
[00:07] <[mbm]> there will be a 1.0-preview released soon just to show people what we've been working on with buildroot-ng
[00:07] <[mbm]> which will mark the first time that we've ever posted binaries of anything but whiterussian
[00:08] <[mbm]> so I expect that to generate tons of interest
[00:08] <groz> is the plan to do more than wrt arch for that preview ?
[00:08] <[mbm]> since most people haven't seen that stuff before
[00:09] <[mbm]> groz: yeah, I'd really like to do as many archs as reasonably stable so we'll also have x86 and uml in there
[00:09] <groz> ok, here's one thought
[00:09] <groz> if we have a bit of a demo on how to work with packages in uml
[00:09] <groz> so it's trivial easy, no need to flash routers
[00:09] <groz> it'll geenrate a lot of developer interest
[00:09] <[mbm]> well, that gets into the next bit of agenda
[00:10] <groz> but the real question first
[00:10] <groz> who is the 'target market' for that ?
[00:10] <groz> users, developers, clueless ?
[00:10] <[mbm]> I'm also looking for someone to be 'editor' of the openwrt.org front page
[00:10] <[mbm]> and get some new content up so it's not the same 2 posts from 6 months ago
[00:10] <groz> I'm in the final throws of a product release cycle here today, if the rest of th eday goes on track
[00:11] <groz> then i'll be deep into the x86 stuff by tomorrow
[00:11] <[mbm]> I'd really like the openwrt.org front page to be more of a development blog with comments by various developers on what they're working on
[00:11] <[mbm]> and some nice articles on how the system works
[00:12] <[mbm]> I've already got a few I've written up
[00:12] <groz> well, the way buildroot-ng goes together
[00:12] <groz> i think if a lot of folks doing thier own thing on embedded stuff see it, and try it
[00:12] <malbon> I can write an article on a few things I am working on. I'll make a start.
[00:12] <groz> we will see a flood of folks jump in
[00:12] <[mbm]> I'm also thinkonf of adding some dynamic content to the front page
[00:13] <[mbm]> we really have a problem right now where it's hard to see that openwrt has actually done anything
[00:13] <groz> hehe, that's gonna change i think
[00:13] <groz> when folks start working with -ng
[00:13] <[mbm]> front page is the same as it's been for months
[00:14] <[mbm]> there's some discussion on the forum but mostly just end user troubles
[00:14] <groz> something that would also be kinda cool
[00:14] <groz> along the lines of what debian does
[00:14] <[mbm]> the release (rc5) is months old
[00:14] <[mbm]> ..
[00:14] <groz> database of packages that have been imported into ng, along with thier functional status for various archs
[00:14] <[mbm]> so I want to add some trac stats to the front page so when you look at it you can see 'ah! something has been done'
[00:15] <groz> we've got a lot in now, but, i'm sure most have only been built, and not really tested, on only one arch
[00:15] <[mbm]> oh, you've reminded me of something else -
[00:15] <[mbm]> I also want to bring back the tracker .. not to keep track of external repos (as it was originally written)
[00:15] <[mbm]> but more of a search engine for the packages that we maintain
[00:16] <[mbm]> debian and ubuntu have a similar online package system
[00:16] <[mbm]> basically this - http://packages.ubuntulinux.org/dapper/x11/xserver-xorg-driver-s3
[00:16] <groz> rite
[00:17] <groz> but, it's a fair amount of work i suspect
[00:17] <[mbm]> not really
[00:17] <groz> or is there a way to create that with trac ?
[00:18] <[mbm]> we should be able to recycle most of that from the old package tracker we used to have
[00:18] <{Nico}> oh, my baby...
[00:18] <Kaloz> :P
[00:19] <[mbm]> {Nico}: think it'd be hard to get the package tracker to spit out pages like that?
[00:19] <[mbm]> should be this: description, dependancies, files includes in the package
[00:19] <[mbm]> with the deps hyperlinked
[00:20] <{Nico}> deps were already
[00:20] <[mbm]> as was the description
[00:20] <{Nico}> we should add arch
[00:21] <[mbm]> yep
[00:21] <{Nico}> package content implies some package retrieval/extraction
[00:22] <[mbm]> hmm right .. all the rest of the info is just parsing the package file
[00:23] <{Nico}> why not add the tracker source to trac?
[00:23] <[mbm]> something else we could do if we're keeping track of package contents - create a folder representing the root directory after every package has been installed
[00:24] <[mbm]> and you can surf around and click on any file in there
[00:24] <[mbm]> and it will tell you what packages install that file
[00:25] <{Nico}> you mean the online imagebuilder we talked about, linked to ther tracker?
[00:25] <[mbm]> not quite
[00:25] <groz> have you ever used rom-o-matic ?
[00:25] <malbon> etherboot's rom-o-matic?
[00:25] <groz> yes
[00:26] <[mbm]> {Nico}: this is more of a reverse package lookup
[00:26] <malbon> that's pretty nifty.
[00:26] <groz> yah, but an online image builder
[00:26] <groz> that just stuffs packages into a blank image
[00:26] <groz> then lets you dl that
[00:26] <groz> very slick
[00:26] <groz> and an absolute bandwidth pig
[00:26] <[mbm]> {Nico}: normal lookup ytou click a package and you get a list of the files in the package, in this case you'd click a file and get the list of packages that create that file
[00:27] <{Nico}> [mbm]: ok
[00:27] <[mbm]> {Nico}: so you might see an apache directory browser showing /etc, you click on inittab and it tells you that inittab is installed by base-files
[00:28] <[mbm]> groz: yeha, we've talked about turning image builder into an online version like rom-o-matic .. we just haven't actually done it yet
[00:29] <{Nico}> [mbm]: i was thinking to an image browser
[00:29] <[mbm]> ?
[00:30] <{Nico}> show the content of an image like you mentionned
[00:30] <malbon> sorry folks, I've got to go. see-ya all.
[00:31] <[mbm]> {Nico}: ah, I don't think of what I just said as an image browser
[00:32] <{Nico}> we would just have to generate a .content file (with find) for every image and use that file with the image browser
[00:33] <{Nico}> i used to put a .content for every packages in the backports directory
[00:33] <{Nico}> that might be used for package content with the tracker
[00:33] <[mbm]> well we already generate a packages.filelist
[00:35] <{Nico}> i admit i'll prefer a plain old tar listing
[00:36] <[mbm]> well, I mean the repository, there's Packages and Packages.filelist
[00:36] <[mbm]> and parsing those two files tells you everything you need to know about all files in that repository
[00:39] <{Nico}> right
[00:40] <[mbm]> hmm .. think that covers all the agenda for this meeting
[00:40] <[mbm]> anyone else have anything to add?
[00:40] <groz> you think ?
[00:40] <[mbm]> groz: on very rare occasions
[00:41] <groz> does it hurt ?
[00:41] <[mbm]> I try not to think about that
[00:41] <groz> lol
[00:43] <[mbm]> so.. recap .. rc6: webif cleaup, testing .. 1.0-preview soon after .. new content for the front page (hire an editor?)
[00:43] <groz> hire ??
[00:43] <[mbm]> well, in the open source sense
[00:43] <groz> one thing that could work well, is, the changelog brought to the front page
[00:44] <groz> possbibly a summary of the last few commits
[00:44] <[mbm]> yeah, that's one of those useless dynamic widgets I talked about
[00:44] <groz> the great thing about dynamic widgets
[00:44] <[mbm]> basically just there to make it look like something has happened since the last time you visited the page
[00:44] <groz> once they are in, you dont have to fusss to get fresh content
[00:44] <[mbm]> serves no other purpose
[00:45] <groz> it serves the purpose of 'fresh stuff' with 'no extra effort'
[00:46] <[mbm]> right
[00:46] <groz> but that gets back to my question earler
[00:46] <[mbm]> still want to get some actual content up though
[00:46] <groz> define the target audience for the ng preview
[00:46] <{Nico}> fresh and but a bit boring maybe
[00:46] <groz> develpers, users, or clueless ?
[00:46] <[mbm]> like I said I want to make the front page into a development blog of sorts
[00:47] <[mbm]> with articles and such
[00:47] <[mbm]> groz: if it works it'll attract tons of new developers, if it fails we get tons of users asking us why google.com doesn't load
[00:47] <groz> LOL
[00:47] <groz> yah, well
[00:48] <groz> i'm thinking most of the interest will be arches other than wrt
[00:48] <[mbm]> right
[00:48] <[mbm]> the wrt arch is dead
[00:48] <groz> i dunno about that
[00:48] <[mbm]> and that's why I want to kill off the whiterussian branch and move on
[00:48] <groz> but it's well supported
[00:48] <groz> well, if you actually want to use it for real today, you gotta use wr
[00:48] <groz> cuz google doesn't load
[00:49] <[mbm]> well, the number of vendors still making hardware from the whiterussian era is quickly dropping
[00:50] <groz> I have confirmation from my sources that the GL will still be available till the new year
[00:50] <groz> now, how reliable are they, dunno
[00:50] <groz> but they have never steered me wrong before
[00:50] <[mbm]> and there seems to be less and less interest in actually doing anything new and exciting with the wrts
[00:51] <groz> well, i can understand why you lost interest in it
[00:51] <[mbm]> so all we really see is end user issues
[00:51] <groz> there's still a bunch of folks actually using the things
[00:51] <[mbm]> using yes, developing? no
[00:52] <[mbm]> so to answer your question the 1.0 preview isn't something for end users to run on a daily basis, it's really something to show developers how great the ng branch is
[00:53] <[mbm]> and the highly unlikely event that it causes some slashdot interest
[00:53] <groz> it shouldn't have any problem doing that
[00:53] <groz> it basically makes the original buildroot env obsolete
[00:53] <groz> and there's still a lot of folks workjing with buildroot variants
[00:54] <[mbm]> we already made the original firmware obsolete long ago
[00:54] <groz> that will switch in a heartbeat when they see it
[00:55] <[mbm]> as kaloz described it, it's really a "call for package maintainers"
[00:55] <groz> rite
[00:56] <groz> so the goal should be, to make it as easy as possible for folks to 'cmon in and play'
[01:05] <CIA-17> nico * r4546 /packages/net/squid/Makefile: add prereq-check on openssl devel lib to squid, standardize, indent
[01:14] <{Nico}> we already have libraries in packages/libs that don't build packages (like pwlib and openh323)
[01:14] <{Nico}> any objections moving toolchain/libnotimpl to packages/libs?
[01:16] <{Nico}> malbon: ping
[01:16] Action: {Nico} forgot, malbon is already gone
[01:47] <db90h> i am excited about the upcoming releases of openwrt
[01:47] <[mbm]> :)
[01:47] <db90h> i think am finally understanding why i have been so wrong in trying to encourage openwrt to target end users..
[01:48] <db90h> openwrt is (or will be) the definitive base for almost any embedded linux platform
[01:48] <[mbm]> that's the plan
[01:58] <CIA-17> nico * r4547 /packages/libs/axtls/ (Makefile files/config): update axtls to v1.01
[02:36] <CIA-17> nico * r4548 /packages/libs/axtls/Makefile: axtls is now on sourceforge, change urls
[16:45] <common> nbd: SYN?
[16:57] <nbd> common: SYN/ACK
[17:02] <common> gave the openrg bootloader a shot?
[17:02] <nbd> not yet
[17:03] <common> ping me if you do, i'll test it
[17:12] <nbd> k
[23:13] <CIA-17> florian * r4549 /packages/net/elinks/Makefile: Restore plain old configure script
[23:35] <CIA-17> florian * r4550 /packages/utils/wx200d/ (. Config.in Makefile ipkg/): Port wx200d to -ng
[00:00] --- Thu Aug 10 2006