d a look at what would be required to implement a basic
PyGTK-based wpa_supplicant GUI. One annoying thing is that (arguably)
the easiest way for an external app to communicate with wpa_supplicant
is via dbus, but wpa_supplicant in FreeBSD is built without dbus
support; another opt
m with additional tools that
> target certain use cases, and PBI seems a good
> fit for the desktop case.
>
> Tim
Genuine (possibly stupid) question -in PBI land, what happens if
package B is, say, CUPS? Does one need versioned rc.d scripts to start
one or the other? Which one gets
to install C5.3 with B4.0 alongside
A1.1 and B3.2.
I'll try to find the paper I'm recalling after work, until then I'll
just have to wave my hands in the air.
-James Butler
working on a new package system in MidnightBSD for some time. When we
weighed this issue, it was
m with additional tools that
> target certain use cases, and PBI seems a good
> fit for the desktop case.
>
> Tim
Genuine (possibly stupid) question -in PBI land, what happens if
package B is, say, CUPS? Does one need versioned rc.d scripts to start
one or the other? Which one gets
ow managers that I might be able
>> to get dockapps to work with if I make this change? I'd like to
>> try it out.
>
> fvwm2 in one I'm quite sure about.
Openbox does natively, and Xfce can with a panel plugin.
-James Butler
_
2009/7/24 Sahil Tandon :
> On Thu, 23 Jul 2009, Adam Townsend wrote:
>
>> I'm using the ports online (from the freebsd.org site) to get ports for my
>> my computers running FreeBSD (running on dial-up). I found that the Python
>> 3.1 source links are all broken. They all contain
>> "/ftp/python//P
