On 2/5/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > Wireless-Tools makes sense. I'm thinking it should be called > WirelessConfig. It'll only deal with iwconfig settings. Everything > else (ifconfig, dhcpcd) should be handled by NetworkInterface. Then > changes won't need to be synced. [...] > > An alias won't work (needs to be executable from outside a shell) but > a wrapper would work great. Which package? And if its one of ours, > wouldn't living in bin be less confusing?
Hmm, it sounds strange to put a "foreign" binary inside Wireless-Tools' bin dir. Being a task it should be ok, but then we would need to store settings somewhere. Are you fine on using a task instead, plus a new file at Wireless-Tools/Settings to store the network settings? Another option is to merge this into Scripts/bin instead, having the script a first check to verify whether the user has Wireless-Tools installed. I was only a little reluctant on this because network settings are currently stored in BootScripts. Maybe we should also take the time and perform a general cleanup on this, putting everything inside Scripts and/or in a new NetworkScripts package? I'm adding gobolinux-devel to the cc: so that the discussion can be followed by other developers not signed to this list. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
