Re: Macports needs a little marketing
Back when it still worked, Porticus was my favorite GUI for MacPorts; but that was long ago, and it wasn't updated to work after a particular MacPorts update. > On Nov 7, 2016, at 05:01, Ryan Schmidt wrote: > > > >> On Nov 7, 2016, at 00:59, [ftp83plus] wrote: >> >> Newbie here: how it is different from Pallet? > > JPortsUI is written in Java; Pallet is not. I expect the UI also differs; I > haven't compared them. > > >> I don't know if pallet is still developed as no one seems to talk about it, > > Pallet is currently not compatible with Xcode 5 or later, and there are > numerous other problems; see open tickets. Help wanted. >
Re: Weird uninstall error
> On Nov 7, 2016, at 7:07 PM, Dave Horsfall wrote: > > (Apologies for possible duplicate) > > Doing my regular "port -u uninstall", I never saw this one before: > >---> Cleaning p5.22-datetime >---> Unable to uninstall p5.22-specio @0.280.0_0, the following ports > depend on it: >---> p5.22-datetime-locale @1.80.0_0 >---> p5.22-datetime-timezone @2.50.0_0 >Error: org.macports.uninstall for port p5.22-specio returned: Please > uninstall the ports that depend on p5.22-specio first. And does first uninstalling the ports that depend on p5.22-specio work?
Re: Macports needs a little marketing ....
On 06/11/16 17:28, Lawrence Velázquez wrote: On Nov 6, 2016, at 11:50 AM, Ken Cunningham wrote: While MacPorts itself could certainly benefit from better PR, I do not see why we should do free advertising for upstream developers. but you see - macports exists to allow people to more easily install the products of these upstream developers. otherwise macports has no use. Taking on a labor-intensive editorial role does not make MacPorts better at installing open-source software. If you want people to buy gas, you sell them cars. (Or electricity -> electric cars, if you're feeling green this season). A tortuous analogy. I don't see Exxon-Mobil or BP selling cars anywhere. True, AIUI they've tended to oppose non-petrol cars rather than advertise for petrol cars https://en.wikipedia.org/wiki/Who_Killed_the_Electric_Car%3F#Oil_companies IMO, the order of consumption is the wrong way around-- the software is more like the fuel (the driving power), the package manager the car (the vehicle that gets you where you want to go). But fuel costs money, and you don't want to remind people of that when selling a car. Whereas FLOSS doesn't explicitly cost money-- to install and run, at least. The software is also like the journey and destination-- the sweeping vistas you can purportedly zoom along through-- and car manufacturers certainly try to associate those with their products. Russell
Re: Macports needs a little marketing ....
> > Taking on a labor-intensive editorial role does not make MacPorts better at > installing open-source software. > Although that statement in and of itself is true, I didn’t that as the topic of this email line, nor the standard by which all is to be judged. However - indeed - message received. Back to my hole.
Re: avahi?
> On Nov 7, 2016, at 8:45 PM, Richard L. Hamilton wrote: > > Anyone get the avahi daemon running, esp. on El Capitan or later? I was > hoping to use it to proxy some stuff (i.e. register mDNS addresses for VPN > clients, so that their usual whatever.local hostname would be available when > connected in remotely, simplifying some matters like maybe xymon monitoring > of them when connected), but I can't get it to stay running. Using launchd > and the plist, I don't even get a useful error message. Trying to run it by > hand, I get: > > Found user 'avahi' (UID 507) and group 'avahi' (GID 504). > Successfully dropped root privileges. > avahi-daemon 0.6.31 starting up. > WARNING: No NSS support for mDNS detected, consider installing nss-mdns! > Dynamic session lookup supported but failed: Unable to find launchd socket > when setuid > dbus_bus_get_private(): Not enough memory > WARNING: Failed to contact D-Bus daemon. Is dbus running? port notes dbus — Brad
Re: Macports needs a little marketing ....
Am 08.11.2016 um 06:57 schrieb Ryan Schmidt: Also, who decides what is stable? Stable, as I see it, means every port in every available variant builds out of the box and does not have major incompatibilities with other ports. Who decides when to update it? Apple. A new stable version should be released for every iteration of macOS. smime.p7s Description: S/MIME Cryptographic Signature
Re: Macports needs a little marketing ....
On Tue, Nov 08, 2016 at 08:26:21PM +0100, Bachsau wrote: > Stable, as I see it, means every port in every available variant > builds out of the box That alone is not testable. For example, the nginx port has 32 variants. For each variant, you can either enable it, or not, so for each variant you have two choices. The first variant gives you two choices. Adding a second variant brings you up to four. The third variant doubles the number of choices again, so you're at 8. For 32 variants, that 2^32 = 4294967296 possibilities. On my MacBook Pro, a build of nginx takes 13.25 wallclock seconds. That's 1850 years to do a testbuild of every possible combination, and that's just for one port on one OS version, and you're suggesting that we do this for every port on every OS version. > and does not have major incompatibilities with other ports. This requires time to test (i.e. manpower) which is already a scarce resource for MacPorts. > > Who decides when to update it? > Apple. A new stable version should be released for every iteration of > macOS. And when do we backport fixes? Do we fix all bugs, critical bugs, security bugs only, or not even those? Who does the work of backporting bugfixes to older versions? (And you're guessing it, that work requires manpower, too.) -- Clemens
