Re: usage numbers for macports vs. homebrew?
They seemed to acquire a lot of traction on the basis of marketing; specifically: - Truthiness (an assortment of “advantages” that turned out not to be, claims that ignored technical accuracy and nuance, and claims quite simply rooted in ignorance), and - Outright negative advertising (“MacPorts driving you to drink?”) It’s a new brand of open-source that I don’t really recognize and can’t say I like; it detracts from the community’s ability to collaborate productivity, and undermines the objective, rational honesty that should be at the core of any engineering endeavor. I don’t really know how to raise the level of discourse; it’s far more expensive to counter to truthiness and negativity than it is to generate it in the first place. Nowadays, people who have never even used MacPorts will repeat verbatim the negative advertising propagated by Homebrew. I find the whole thing distasteful. -landonf On Mar 18, 2014, at 8:25 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Marketing. Ease of use. Davor Cubranic cubra...@stat.ubc.ca wrote: On Mar 12, 2014, at 2:12 PM, Art McGee amc...@gmail.com wrote: The problem is that the presentation of the case for supporting MacPorts was confusing and unconvincing, so usage statistics are not going to help in that matter. I’ve been wondering why Homebrew has such huge momentum and mindshare these days. In random places on the web I’ve seen people imply that it’s better/more reliable than Macports. (The only concrete example was terribly outdated, about TexLive version about four years ago.) I’ve given Homebrew a quick try in a VM and it doesn’t seem that different in functionality. (Except that I do wish we had something like Homebrew-cask.) So, other than the coolness factor (which I guess comes partly from being “the new thing”, and partly from using Github for all development and distribution), what else is there? Try to keep it factual and based on your own experiences using/administering both, please. Davor ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Mar 18, 2014, at 3:57 PM, Eric A. Borisch ebori...@macports.org wrote: However, perhaps we should take a page from their book. Look at the homebrew homepage (http://brew.sh/) * It would be nice a similar minimalist, here is what macports does for you landing page. * A one line copy-and-paste install option to get a new user going would be nice, too. It could check for and prompt the user for XCode, etc before actually installing. I assume this is what theirs does. * A simple 'port create url' that would create a typical Portfile (configure / make / make install) in a auto-generated local location (and properly setup sources.conf) and then open the new portfile in Editor (perhaps with some helpful comments on things that might need tweaking) I personally think this is a great idea. Not that I am in a position to enact such an idea :-) I also don't think we've done enough to publicize the phenomenal impact the build bots have on a typical install scenario -- and to emphasize the you need to use the defaults if you want binary package usage. Agreed. -landonf___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: phinze/homebrew-cask on the same system like MacPorts
On Dec 19, 2013, at 13:31 , Clemens Lang c...@macports.org wrote: On Thu, Dec 19, 2013 at 10:19:14AM -0800, Bradley Giesbrecht wrote: Clemens: can trace mode be set in macports.conf? No, currently not. Other than performance overhead, would there be any reason to not enable it by default? Cheers, Landon signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Why doesn't macports install prebuild packages?
On Nov 27, 2009, at 2:05 AM, Jasper Frumau wrote: I am not a base developer so for me this is hard to judge or comprehend, but is there not any open source code available used by other package managers or repositories that can be used to start a Mac Ports package manager project? Sure. The question was always what package format to use. At first (~2002) we discussed dpkg, but abandoned because IIRC at the time Debian preferred Apple to not use it. We held out hope for apkg, a more advanced/suitable Apple Package Format, but that didn't materialize. We've discussed on and off a xar-based packaging format, but that, though a very nice idea, has still not happened. In the meantime, we implemented support for generating quite a few different package formats in base very early on -- dpkg, rpm, pkg/mpkg. If you install the dpkg or rpm ports, you can build packages from ports right now. Example: land...@max sudo port dpkg dict ... --- Creating dpkg for dict-1.9.7 land...@max dpkg --info `port dir dict`/work/*.deb new debian package, version 2.0. size 69930 bytes: control archive= 434 bytes. 467 bytes,10 lines control Package: dict Architecture: darwin-i386 Version: 1.9.7-1 Section: textproc Maintainer: landonf Installed-Size: 201 Description: Dictionary Server Protocol (RFC2229) client The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. dict(1) is a client which can access DICT servers from the command line. . http://www.dict.org/ The same also works for 'rpm', and Apple 'pkg' and 'mpkg' targets. Someone just needs to invest the time in implementing automated building of all of the packages into a repository, ensuring that MacPorts meta-data is properly included, and you could provide an package (apt-get, yum, macports 'archive', ...) binary repository. If you look in base/portmgr/packaging, you'll actually find a number of scripts that do most of this: - dpkgall.tcl - mpkgall.tcl - packageall.tcl - rpmall.tcl With some pragmatic decisions about a packaging format, hardware on which to run builds (IIRC j...@apple has offered to donate this), and a bit of time, I'd bet a sufficiently motivated developer (admittedly, not me) could have a binary repository fairly operational within a couple weeks. -landonf ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: A different openjdk6 install problem
On Aug 15, 2009, at 5:58 AM, Joshua Root wrote: This is defined in /opt/local/include/X11/extensions/shmproto.h, which is provided by xorg-xextproto, which is in openjdk6's dependency tree. Double check that it's installed and active. Does the port build if you install xorg-xextproto manually? If so, then it's just missing an xorg-xextproto dependency. I'm running Snow Leopard and OpenJDK bsd-port does not currently support 10.6, so I can't test this (until I or someone else has time to commit fixes to OpenJDK, anyway). -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Port for python26: batteries not included (or available)?
On Oct 4, 2008, at 7:35 AM, Rainer Müller wrote: It's just too early to request py26-* ports. There is a pending patch from jmr to unify the python module ports and reduce the mess we created with py-* and py25-*. http://trac.macports.org/ticket/16723 Before we go on creating py26-* ports this patch should be considered. Won't the use of variants to select between 2.4, 2.5, and 3.0 in the same port result in an inability to install the same Python module for more than one version of Python? -landonf ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Port for python26: batteries not included (or available)?
On Oct 5, 2008, at 7:03 PM, Ryan Schmidt wrote: On Oct 5, 2008, at 14:18, Landon Fuller wrote: On Oct 4, 2008, at 7:35 AM, Rainer Müller wrote: It's just too early to request py26-* ports. There is a pending patch from jmr to unify the python module ports and reduce the mess we created with py-* and py25-*. http://trac.macports.org/ticket/16723 Before we go on creating py26-* ports this patch should be considered. Won't the use of variants to select between 2.4, 2.5, and 3.0 in the same port result in an inability to install the same Python module for more than one version of Python? The description of the above ticket says: Here is a portgroup that should be able to replace the current python25 and python24 groups, and can install for any combination of the available python versions at once via variants. So it sounds like e.g. the +python24 and +python25 variants would not conflict with one another, would not be mutually exclusive. But two installed ports with the same name (but different variants) will conflict. The the port group would also need to change the port's name based on the selected python variant , but that would wreak havoc with indexing, etc. -landonf ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Dependencies relationship to default variants?
On Jul 11, 2008, at 2:13 AM, Rainer Müller wrote: You are right, there is no dependency on kerberos5. And it is using the Kerberos framework provided by Apple. Our current policy is not to use system libraries, but add them to MacPorts and use it from there. I am CC'ing the maintainers of cyrus-sasl2. Juan, Landon, would it be possible to use kerberos5 here instead? On Mac OS X, Kerberos is a more or less a runtime system service, integrating with the Keychain, the GUI, etc. It's an instance where I believe it makes sense to use the system libraries. -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Not a Fan of Cyrus-Sasl
On Jun 30, 2008, at 6:07 PM, Tom Allison wrote: I noticed that the last upgrade of subversion picked up cyrus-sasl on my macbook. I'm interested to know how I can lock ports to a specific version of subversion (or other software) so that I can avoid something like this? I'm curious -- why is this an issue in your environment? -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: clam says boot.efi Broken.Executable
On Jun 29, 2008, at 2:43 PM, Brian Flaherty wrote: This is also what the --detect-broken option for clamscan is supposed to detect. It doesn't seem odd (to me) that a boot file would be structured differently than a standard executable. EFI uses a subset of the PE32+ image format with a modified header signature. The modification to signature value in the PE32+ image is done to distinguish EFI images from normal PE32 executables. The “+” addition to PE32 provides the 64 bit relocation fix-up extensions to standard PE32 format. Intel EFI Spec v1.02, Section 4.2, EFI Image Header: http://download.intel.com/technology/efi/docs/pdfs/EFISpec_v102.pdf Cheers, -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts caching of distfiles [was Re: ntfs-3g 1.1120 source missing]
On Feb 25, 2008, at 1:34 PM, Rainer Müller wrote: I didn't know they are using such a flat namespace. They're not -- When there are distfile collisions (and there are), they use DIST_SUBDIR to partition a particular port's distfiles. MacPorts by default simply places all distfiles in a port-specific subdirectory, since only port names are required to not conflict. PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Kerberos5 depends on gnupg but not gnupg2
On Jul 22, 2007, at 3:56 PM, Tabitha McNerney wrote: Yves, great, I'll see if I can get the Portfile to use gnupg2 instead of gnupg. Is the kerberos5 MacPort not really used much by anyone now? I see that Apple now includes a Kerberos Key Distribution Center (KDC) in Mac OS X Server (I think starting with 10.3 - Panther) which might suffice for most people, although some of the MacPorts can be built with the kerberos variant which then indeed depends on the kerberos5 MacPort having been installed. I see there is also an implementation of Kerberos which is available in MacPorts as the heimdal port. Do most in the MacPorts community now have a preference for the heimdal port over the kerberos5 port? I've a preference for the Heimdal implementation. Compare Heimdal: http://www.securityfocus.com/cgi-bin/index.cgi? o=0l=30c=12op=display_listvendor=Heimdalversion=title=CVE= vs MIT Kerberos: http://www.securityfocus.com/cgi-bin/index.cgi? o=0l=30c=12op=display_listvendor=MITversion=title=Kerberos% 205CVE= http://www.securityfocus.com/cgi-bin/index.cgi? o=0l=30c=12op=display_listvendor=MITversion=title=Kerberos% 204CVE= As for gnupg vs gnupg2, both branches are still maintained; gnupg 1.x is -- for now -- probably a safer and more conservative choice. -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: cyrus-sasl2 fails to install (surprising to me)
On Jun 15, 2007, at 10:27 PM, Tabitha McNerney wrote:
Ryan,
Thanks a ton. That was indeed the problem. However, I noticed that
the cyrus-sasl2 Portfile which had problems building today is the
same (when I diffed it) with the cyrus-sasl2 Portfile that has been
around for quite some time (several months to almost one year?).
The same Portfile builds just fine on an earlier version of
MacPorts ( 1.4) and on both Intel and PowerPC architectures. I
fixed the Portfile after your suggestion like this:
#variant kerberos darwin {
variant kerberos {
configure.args-append --enable-gssapi --with-gss_impl=mit
}
What I don't understand is, why would this problem in the Portfile
manifest itself now v.s. 8 months ago for example?
Thanks again Ryan for noticing what now seems to be obvious in that
there should not be blank spaces in the names of variants.
This old syntax was correct -- if it was broken, it is a bug.
The double variant syntax is used to create a variant that will be
applied *instead of* two singular variants. That is, if both darwin
and kerberos are selected, then the darwin kerberos variant will
be used instead of individual darwin {} and kerberos {} variants.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: hosting an internal macports server with binaries
On May 8, 2007, at 00:38, Jordan K. Hubbard wrote: On May 7, 2007, at 7:23 PM, Ryan Schmidt wrote: Such a format does exist: It's called a .pkg file and you interact with them every time you install an Apple software update. However, I don't think there's any functionality in MacPorts to create or use package files. Oh really? [snip] You can also do use the mpkg target for ports with dependencies; this will cause a metapackage to be built which contains all the deps, making the package stand-alone. This functionality has been in macports for a long time. :) And dpkg (and rpm) too! There's even a particularly frightening script I wrote to build dpkg apt-get repositories from a list of ports in base/portmgr/dpkgall.tcl Of course, xar is the better choice, now. Freak out! [EMAIL PROTECTED]:dict sudo port dpkg dict [snip] --- Creating dpkg for dict-1.9.7 Of course, it seems to be slightly broken, now: [EMAIL PROTECTED]:macports/dports/textproc/dict sudo dpkg --force-all -- install work/dict_1.9.7_darwin-i386.deb dpkg - warning, overriding problem because --force enabled: package architecture (darwin-i386) does not match system (i686-darwin) Selecting previously deselected package dict. (Reading database ... 0 files and directories currently installed.) Unpacking dict (from .../dict_1.9.7_darwin-i386.deb) ... dpkg: dict: dependency problems, but configuring anyway as you request: dict depends on libtool (= 1.5.22); however: Package libtool is not installed. Setting up dict (1.9.7) ... [EMAIL PROTECTED]:macports/dports/textproc/dict dpkg --list Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half- installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=- =- == ii dict 1.9.7 Dictionary Server Protocol (RFC2229) client PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: FUSE ports [was Re: sshfs]
On May 7, 2007, at 01:27, Ryan Schmidt wrote:
Note also that probably none of the MacPorts contributors have case-
sensitive HFS+ setups, so probably nobody other than you will
discover or be affected by such problems. While I would expect such
problems to be rare, they would be nonexistent if you used the
normal case-insensitive HFS+.
Heh. Actually:
http://trac.macports.org/projects/macports/browser/trunk/dports/
devel/cvs-port
Was named 'cvs-port' as to not conflict with 'CVS' the directory,
when we used CVS ('CVS' vs. 'cvs').
On the flip side, some people are going to use case-sensitive file
systems. There doesn't seem like a particularly good reason to not
support them, since 9 times out of 10, failure to work with a case-
sensitive file system is indicative of a bug.
-landonf
PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Gimp Fails to Build
On May 1, 2007, at 14:51, Ryan Schmidt wrote: On May 1, 2007, at 15:46, Yves de Champlain wrote: gimp is now the same port as gimp2 when 2.4 comes out, I will remove both gimp-dev (2.3.x) and gimp2 What will happen for users who currently have gimp2 or gimp-dev installed? Can anything happen? They'll have to switch to the 'gimp' port. PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: recommended dependencies?
On Feb 13, 2007, at 00:59, Kevin Ballard wrote: No. it would contain the code that activates the rtf support. If the user doesn't want it, they can specify -with_rtf. Why wouldn't the user use -rtf ? That was the purpose of our implementing variant negation to being with. I assumed with_ / without_ was implied/assumed based on + or -. -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: recommended dependencies?
On Feb 13, 2007, at 14:21, Landon Fuller wrote:
On Feb 13, 2007, at 00:59, Kevin Ballard wrote:
No. it would contain the code that activates the rtf support. If
the user doesn't want it, they can specify -with_rtf.
Why wouldn't the user use -rtf ?
That was the purpose of our implementing variant negation to being
with. I assumed with_ / without_ was implied/assumed based on +
or -.
And moreover, default_variants allows for the variant to be explicit:
default_variantsrtf
variant rtf {
}
Then a user can disable RTF support with -rtf. If you want RTF to
require explicit enabling, remove the default_variants and the user
will have to use +rtf.
-landonf
PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: liboil fails to build/upgrade
On Feb 1, 2007, at 17:15, Paul Beard wrote: if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H - I. -I. -I.. -I/opt/local/include -L/opt/local/lib -Wall - force_cpusubtype_ALL -D_BSD_SOURCE -D_GNU_SOURCE -I.. -L/opt/local/ lib -MT liboil_0.3_la-liboilcpu.lo -MD -MP -MF .deps/liboil_0.3_la- liboilcpu.Tpo -c -o liboil_0.3_la-liboilcpu.lo `test -f 'liboilcpu.c' || echo './'`liboilcpu.c; \ then mv -f .deps/liboil_0.3_la-liboilcpu.Tpo .deps/liboil_0.3_la- liboilcpu.Plo; else rm -f .deps/liboil_0.3_la-liboilcpu.Tpo; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include -L/opt/local/ lib -Wall -force_cpusubtype_ALL -D_BSD_SOURCE -D_GNU_SOURCE -I.. -L/ opt/local/lib -MT liboil_0.3_la-liboilcpu.lo -MD -MP -MF .deps/ liboil_0.3_la-liboilcpu.Tpo -c liboilcpu.c -fno-common -DPIC - o .libs/liboil_0.3_la-liboilcpu.o /var/tmp//ccDl8DLX.s:416:Parameter syntax error (parameter 1) make[3]: *** [liboil_0.3_la-liboilcpu.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. Error: Unable to upgrade port: 1 Ugh; PowerPC? -landonf PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: liboil fails to build/upgrade
On Feb 1, 2007, at 9:58 PM, McGarry Vince wrote: On Feb 1, 2007, at 11:01 PM, Paul Beard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 1, 2007, at 5:16 PM, Landon Fuller wrote: Ugh; PowerPC? yes, it is. white:~ paul$ uname -a Darwin white.paulbeard.org 8.8.0 Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC Power Macintosh powerpc Interestingly, I built it as a pkg on another PPC system and it built just fine there. Moved the package over to this machine and installed it. No idea if that helps at all ;-) I, too, cannot get it to build on a PowerPC. What version of gcc / Xcode? -landonf ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
