Re: Ubuntu 18.04.4 on older Apple hardware

2020-04-05 Thread db
On 5 Apr 2020, at 14:00, macports-users-requ...@lists.macports.org wrote: > Message: 1 > Date: Sun, 5 Apr 2020 01:21:40 -0700 > From: Ken Cunningham > To: macports-users@lists.macports.org > Subject: Ubuntu 18.04.4 on older Apple hardware > Message-ID: > Content-Type: text/plain;

Re: macports-users Digest, Vol 150, Issue 4

2019-02-05 Thread db
On 4 Feb 2019, at 13:00, macports-users-requ...@lists.macports.org wrote: > Message: 5 > Date: Sun, 3 Feb 2019 20:24:48 -0800 > From: Al Varnell > To: James Linder > Cc: macports-users@lists.macports.org > Subject: Re: browser recomendations > Message-ID:

Re: How Mojave-ready is MacPorts?

2018-11-12 Thread db
On 12 Nov 2018, at 22:32, Ryan Schmidt wrote: > What we really want is a web site where this information can more easily be > seen. > I don't really want the public making massive numbers of http requests to the > buildmaster (which is what the script would do) I just want that every build

Re: How Mojave-ready is MacPorts?

2018-11-12 Thread db
On 11 Nov 2018, at 13:00, macports-users-requ...@lists.macports.org wrote: > Message: 11 > Date: Sat, 10 Nov 2018 15:27:51 -0600 > From: Ryan Schmidt > To: Dave Horsfall > Cc: MacPorts Users > Subject: Re: How Mojave-ready is MacPorts? > Message-ID:

Re: portindex fails due to portfile parsing

2018-03-19 Thread db
On 19 Mar 2018, at 16:56, Ryan Schmidt wrote: > Probably an unintended consequence of one of my changes last month. > What version of macOS and what version of Xcode are you using? OS X 10.8.5, Xcode 5.1.1.

portindex fails due to portfile parsing

2018-03-19 Thread db
Today I tried syncing and it failed, see log below. It succeeded when I moved the portfile away. Base is from source. $ sudo port -v sync ---> Updating the ports tree Synchronizing local ports tree from file:///opt/local/myports Creating port index in /opt/local/myports Total number of ports

telling devs about macports installation alternative - was Re: Is there and "rdist" for Mac?

2018-03-19 Thread db
On 18 Mar 2018, at 23:28, ↪︎nudge <nudge...@fastmail.fm> wrote: > On Sun, 18 Mar 2018, at 23:08, db wrote: >> Good to know. Unfortunately, although gitless is already in MP, the >> developer doesn't mention it, but alas, HB >> (https://github.com/sdg-mit/gitless#in

Re: Is there and "rdist" for Mac?

2018-03-18 Thread db
On 17 Mar 2018, at 20:48, ↪︎nudge wrote: > Another option worth considering > http://gitless.com/ Good to know. Unfortunately, although gitless is already in MP, the developer doesn't mention it, but alas, HB

Re: index warning and bash-completion

2018-03-11 Thread db
On 11 Mar 2018, at 04:01, Ryan Schmidt <ryandes...@macports.org> wrote: > On Mar 10, 2018, at 17:47, db wrote: >> Btw, how can I change the two-week period for the warning. I couldn't find >> an option in macports.conf, either to change the period or to suppress it >>

Re: index warning and bash-completion

2018-03-10 Thread db
On 10 Mar 2018, at 23:15, Clemens Lang wrote: > > https://github.com/macports/macports-ports/blob/master/sysutils/bash-completion/files/port > so if you have time you could try modifying it to drop stderr into nirvana > and submit a pull request for that. Ok, I'll have to

Re: index warning and bash-completion

2018-03-10 Thread db
On 10 Mar 2018, at 20:05, Ryan Schmidt wrote: > Are your port definitions in fact more than two weeks old? Yes, but I'd expect the warning after I actually ran the command.

index warning and bash-completion

2018-03-10 Thread db
bash-completion for port outputs stderr on pressing tab, right before it completes a word, on certain actions like contents. $ port contents bash-complWarning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. etion Can anyone reproduce it?

Re: request for port peg command, to lock down a port at the currently installed version

2018-03-06 Thread db
On 6 Mar 2018, at 15:50, Ken Cunningham wrote: > port peg PORTNAME brew pin FORMULA? There shouldn't be shame in mentioning it. As Arno pointed out, it gets tricky with deps, it's eventually overridden if necessary. As I raised in another topic, port upgrade

Re: running macports along with homebrew

2018-03-06 Thread db
On 6 Mar 2018, at 10:49, Ryan Schmidt wrote: > The portindex indexes Portfiles, not portgroups. So the port's version must > be set in the Portfile, not anywhere else. Would then portindex fail if the port's version in the portfile is a variable set to a command?

Re: running macports along with homebrew

2018-03-06 Thread db
On 6 Mar 2018, at 02:34, Ryan Schmidt <ryandes...@macports.org> wrote: > On Mar 5, 2018, at 05:43, db wrote: >> As I said in my previous post, you can get HEAD's hash with 'git ls-remote >> --heads'. And store it somewhere. > Who are you suggesting should run this co

Re: running macports along with homebrew

2018-03-05 Thread db
On 5 Mar 2018, at 11:39, Ryan Schmidt wrote: > hash+date is specific, predictable, repeatable. The portfile developer tests > a specific hash+date, and when satisfied, commits it to make it available to > MacPorts users. As I said in my previous post, you can get

Re: running macports along with homebrew

2018-03-05 Thread db
On 4 Mar 2018, at 05:16, Ken Cunningham wrote: >github.setupauthor project HEAD >checksum {} Thanks, Ken. I didn't think it'd be that easy. Only caveat is that it fails the livecheck and there's no way to correlate HEAD to a date. The commit

Re: how to make a portfile for a github project?

2018-03-03 Thread db
On 3 Mar 2018, at 00:48, Mojca Miklavec wrote: > At some point this documentation about the GitHub PortGroup should end up in > the online guide: >https://github.com/macports/macports-guide/pull/12/files Yeah, in the long meantime

Re: Search for a MacPorts Mascot: looking for talented artists

2018-02-21 Thread db
On 21 Feb 2018, at 17:32, Mojca Miklavec wrote: > Something in the spirit of ... >http://en.wikifur.com/w/images/4/46/Hexley_fork_450.png I like that MacPorts lacks a mascot identity. But if you really need, want one, then I probably choose Darwin's Hexley. Another that

Re: running macports along with homebrew

2018-02-14 Thread db
On 14 Feb 2018, at 20:46, Ken Cunningham wrote: > In a recent poll > , homebrew was > recommended 375 to 25 over MacPorts. > Most developers who offer their software for download and building manually

Re: running macports along with homebrew

2018-02-14 Thread db
On 14 Feb 2018, at 19:20, Ken Cunningham wrote: > For git, I'd have to look at the github portgroup to see how to do that. > But as you heard from Ryan, it appears it's not ever going to make it into > macports in general… Yeah, the thing is having at the very

Re: running macports along with homebrew

2018-02-14 Thread db
On 14 Feb 2018, at 14:56, Ryan Schmidt wrote: > I'm aware of "cask" being a feature of Homebrew. If that's what you're > referring to, what does the feature do / what do you want MacPorts to do in > regard to this? Manage (and here the terminology gets trickier) more

Re: running macports along with homebrew

2018-02-13 Thread db
On 13 Feb 2018, at 19:52, Ken Cunningham wrote: > 1. cask: > […] > I think nobody finds this in general to be all that magical or useful though, > and so nobody bothers to spend any time on building these sorts of Portfiles. > You want Adobe Air? Just go to the

Re: running macports along with homebrew

2018-02-13 Thread db
On 13 Feb 2018, at 07:01, Ken Cunningham wrote: > If there is anything worth having in MacPorts that is in Homebrew but not > MacPorts, just ask for it. I'm trying homebrew as a fallback for MacPorts, but since you said anything, here's a wish list: cask,

Re: running macports along with homebrew

2018-02-13 Thread db
On 12 Feb 2018, at 23:08, Jeremy Lavergne wrote: > MacPorts can deny any access to Homebrew during builds in trace mode. > Less invasive than renaming files or folders. >> port -t install PORTNAME Depending on who you ask, there's much overhead, in any case, >%50.

Re: running macports along with homebrew

2018-02-12 Thread db
On 12 Feb 2018, at 16:13, Mojca Miklavec wrote: > Exceptions might occur for formulas that put stuff outside of /usr/local AFAIR from the documentation everything that's built locally is contained in so-called cellars under its prefix, so I could just rename it

Re: running macports along with homebrew

2018-02-12 Thread db
Would it suffice to rename /usr/local during build time to avoid any conflicts? I ask because I just want to make sure that I'm not missing anything else.

Re: Build Failure on ports-10.8_x86_64_legacy: lowdown

2018-01-24 Thread db
https://trac.macports.org/ticket/51516#comment:19 On 24 Jan 2018, at 18:10, Jan Stary wrote: > Looking at > https://build.macports.org/builders/ports-10.8_x86_64_legacy-builder/builds/49810/steps/install-port/logs/stdio > it seems that the buildbot failed to even download the

Re: scp ignores case in filenames?

2018-01-19 Thread db
On 19 Jan 2018, at 17:09, "Richard L. Hamilton" wrote: > At a mere guess, I'd say there'd be very little of that. Most of the code > originated on Linux or one of the *BSD's; and most of them would default to > case-sensitive filesystems, even if they had the option. So

Re: scp ignores case in filenames?

2018-01-19 Thread db
On 19 Jan 2018, at 15:23, Vincent Habchi wrote: > I’ve been working for years on case-sensitive HFS+/APFS file systems (coming > from BSD Unix) and never encountered any problem. Only PyCharm needs an extra > configuration line to be inserted. But that’s the only side effect

Re: trace mode by default

2018-01-09 Thread db
On 9 Jan 2018, at 08:52, Joshua Root wrote: > 'porttrace yes' in macports.conf should do it. Note that then there's no way > to turn it off from the command line. Can not all ports be built in trace mode? Clemens mentioned go. Do you have any numbers for the performance

trace mode by default

2018-01-08 Thread db
I couldn't find this neither on port's manpage nor in macports.conf. Is there an option to set trace mode by default? Could the performace penalty be roughly quantified?

meltdown and spectre

2018-01-05 Thread db
In case anyone hasn't heard of it yet, https://meltdownattack.com/ https://lwn.net/Articles/742999/

Re: livecheck timeout

2017-11-23 Thread db
On 23 Nov 2017, at 17:06, Ryan Schmidt wrote: > ftp connections fail in many circumstances, due to either the use or non-use > of passive mode, or for other reasons. I'm certainly tired of attempting to > debug them, which is why it's great when we can remove the use of

Re: livecheck timeout

2017-11-23 Thread db
On 23 Nov 2017, at 16:52, Ryan Schmidt wrote: > $ time port livecheck gnutls > real 0m1.252s > user 0m0.196s > sys 0m0.079s Hmm…master_sites was updated,

Re: livecheck timeout

2017-11-23 Thread db
On 23 Nov 2017, at 15:14, Rainer Müller wrote: > The connect timeout of 30 seconds for downloads using libcurl is hardcoded in > base [1] and cannot be configured. > [1] >

Re: livecheck timeout

2017-11-23 Thread db
On 23 Nov 2017, at 06:42, Ryan Schmidt wrote: > How long is too long? 30'

Re: installing binary archives as non-root user

2017-11-19 Thread db
On 18 Nov 2017, at 20:38, Ryan Schmidt wrote: > Yeah, really, nope. Ports are able to make decisions based on the install > user; some ports do different things when installing as root vs. installing > as a normal user. I've been reading some of Homebrew's

Re: MacPorts installation processes

2017-11-11 Thread db
On 11 Nov 2017, at 15:08, Mojca Miklavec wrote: > But after that the lives of the 2.4 branch and the master branch start > diverging. The release 2.4.3 will still be "wildly different from master". > The releases x.y.z where z > 0 are not created from the master

Re: MacPorts installation processes

2017-11-11 Thread db
On 11 Nov 2017, at 10:40, Ryan Schmidt wrote: > "2.4.99" means some point along the way of developing 2.5.x, but not any > particular point; you can update your git clone and rebuild to get a newer > "2.4.99". Bear with me. If I understood correctly, if I checkout a

Re: MacPorts installation processes

2017-11-10 Thread db
On 10 Nov 2017, at 23:18, Mojca Miklavec <mojca.miklavec.li...@gmail.com> wrote: > On 10 November 2017 at 23:00, db wrote: >> Is it possible to install a snapshot from master and later upgrade to a >> release? > Only to a release that's derived from master. That is: if

Re: MacPorts installation processes

2017-11-10 Thread db
On 10 Nov 2017, at 14:04, Rainer Müller wrote: > Unfortunately, there is no way to roll back these changes to the registry. > Either you have to keep using development versions, or you have to uninstall > MacPorts completely, then reinstall the latest stable release and all

files manually installed in $prefix

2017-10-29 Thread db
I wrote a plugin file for a port and put it in the same directory as the default ones, because I considered it convenient at that time, not realising that it could be invoked by its full path from another location. How can I get files manually installed in $prefix? I'm asking out of curiosity.

Re: buildbot build time

2017-10-27 Thread db
On 27 Oct 2017, at 15:54, Ken Cunningham wrote: > https://wiki.gentoo.org/wiki/Genlop Thanks Ken, I'll keep that in mind. My purpose was a much modest shell script that parses outdated ports and retrieves build or cpu time (or any stat that could give an

Re: buildbot build time

2017-10-27 Thread db
I still think some indication of build time is useful, for example, _relative_ to other ports that I might estimate or know its build time. For how long is build information retained, like in https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/10627 ?

buildbot build time (was: establish installed dependency not in portfile)

2017-10-25 Thread db
On 25 Oct 2017, at 07:35, Mojca Miklavec <mojca.miklavec.li...@gmail.com> wrote: > On 23 October 2017 at 10:40, db wrote: >> On 9 Oct 2017, at 12:46, Mojca Miklavec wrote: >>> That info is easy to read and collect from the buildbot. The keyword is: >>>

Re: macports owns my user folder in most of my backups

2017-10-15 Thread db
On 15 Oct 2017, at 23:16, Lenore Horner <lenorehor...@sbcglobal.net> wrote: > On Oct 15, 2017, at 03:28, db <iams...@gmail.com> wrote: >> Check this post for some background, >> https://lists.macports.org/pipermail/macports-dev/2017-September/036431.html. > We

Re: macports owns my user folder in most of my backups

2017-10-15 Thread db
On 15 Oct 2017, at 00:41, Lenore Horner wrote: > I use Time Machine to backup my hard drive to an external drive. At some > point (and I don’t know when) MacPorts became the owner of my folder in Users > for most or all of my backups. Folders above that level are

Re: High Sierra and MacPorts

2017-10-12 Thread db
On 12 Oct 2017, at 12:51, Ryan Schmidt wrote: > https://lists.macports.org/pipermail/macports-users/2017-September/043743.html > The High Sierra buildbot worker is still busy building ports. If you want to > have a higher probability that you can receive binaries from

Re: cannot sync - pulling is not possible because you have unmerged files

2017-10-10 Thread db
On 10 Oct 2017, at 17:42, "Daniel J. Luke" wrote: > If the OP does have a need to be syncing from the git repository, he should > be able to manage any conflicts like this without help from the list. As I said, I didn't modify the checkout.

Re: cannot sync - pulling is not possible because you have unmerged files

2017-10-10 Thread db
On 10 Oct 2017, at 15:17, Chris Jones wrote: > So one or more of those modifications are your problem. The modifications in > your checkout conflict with something coming in from the sync. You need to > resolve these conflicts before trying again. I didn't modify the

Re: establish installed dependency not in portfile

2017-10-09 Thread db
On 9 Oct 2017, at 16:17, Rainer Müller wrote: > What is so strange about that? The current PortIndex has ~20K ports and these > statistics also include historical data on obsolete ports that no longer > exist in our ports tree. Exactly that, historical data and obsolete

Re: establish installed dependency not in portfile

2017-10-09 Thread db
On 9 Oct 2017, at 11:16, Chris Jones wrote: > Why do you always build from source instead of use the tarballs when > available ? Its not entirely reasonable on one hand to complain about build > times, and at the same time turn off a feature designed to avoid them...

Re: establish installed dependency not in portfile

2017-10-08 Thread db
On 8 Oct 2017, at 22:05, Ryan Schmidt wrote: > No, we don't have anything that estimates build time. Would a feature request make sense? Having build time and open tickets (defect/platform) when running `port outdated` would spare quite a few headaches. As of now, I

Re: establish installed dependency not in portfile

2017-10-08 Thread db
On 8 Oct 2017, at 21:19, Ryan Schmidt <ryandes...@macports.org> wrote: > On Oct 8, 2017, at 05:17, db wrote: >> Since py27-numpy is the only port installed requiring gcc7, I rather choose >> gcc6 which is used by many others instead. > You can do that, but since gcc7 is t

Re: establish installed dependency not in portfile

2017-10-08 Thread db
On 8 Oct 2017, at 01:17, Ryan Schmidt wrote: > py-numpy requires a Fortran compiler. Xcode doesn't contain one, so we must > use one provided by MacPorts. You can choose which compiler to use by using > variants: > For modern systems, the default gcc port that the

Re: establish installed dependency not in portfile

2017-10-07 Thread db
On 7 Oct 2017, at 15:41, db <iams...@gmail.com> wrote: > On 7 Oct 2017, at 15:15, Jeremy Lavergne <jer...@lavergne.me> wrote: >> Something like `port dependents gcc7` > I forgot to mention it. > $ port rdependents gcc7 > gcc7 has no dependents. It seems that gcc7

Re: establish installed dependency not in portfile

2017-10-07 Thread db
On 7 Oct 2017, at 15:15, Jeremy Lavergne wrote: > Something like `port dependents gcc7` I forgot to mention it. $ port rdependents gcc7 gcc7 has no dependents.

establish installed dependency not in portfile

2017-10-07 Thread db
I updated my ports and realised that gcc7 was built, but couldn't establish for which port it was necessary. I thought something like `port cat installed | grep '^name\|gcc7'` would help reveal it. Then I tried `port rdeps installed | grep ' ports\|gcc7'` and noticed py27-gnuplot, py27-numpy

uninstall inactive port breaks active port

2017-10-07 Thread db
py-readline was replaced by py-gnureadline https://github.com/macports/macports-ports/commit/9beeded98a3eba28030e4993153a037366f5bda5 Can I safely uninstall it? $ port installed inactive The following ports are currently installed: py27-readline @6.2.4.1_1 $ $ sudo port uninstall inactive

Re: ffmpeg fails to configure

2017-10-06 Thread db
On 6 Oct 2017, at 23:06, Ken Cunningham wrote: > we should probably just search the macports database for everything that > requires port:openjpeg and flag them all. Almost all of them are probably > broken again - last openjpeg update just finished and we

Re: ffmpeg fails to configure

2017-10-06 Thread db
On 6 Oct 2017, at 21:52, Ken Cunningham wrote: > Every time openjpeg does a decimal point update, it changes the headers and > everything breaks. What a PITA. -- Ken Thanks. I pinned ffmpeg 3.3.3 in my local repo. Should I file a ticket for 3.3.4?

ffmpeg fails to configure

2017-10-06 Thread db
Could anyone please take a look at this log? It seems that ffmpeg 3.3.4 misses a bunch of headers on 10.8. http://www.mediafire.com/file/u2z139htht93411/config.log

ffmpeg fails to configure

2017-10-06 Thread db
Could anyone please take a look at this log? It seems that ffmpeg 3.3.4 misses a bunch of headers on 10.8. http://www.mediafire.com/file/u2z139htht93411/config.log

Re: Uninstall a port and ONLY THAT PORT's dependencies?

2017-10-04 Thread db
On 4 Oct 2017, at 06:00, Dave Horsfall wrote: > Someone (I've forgotten who) pointed out is was likely that I installed them > before MacPorts honoured the "requested" flag (I've had this MacBook for > quite a few years). Are those ports listed in `port echo requested`?

Re: curl error:1407742E:SSL

2017-10-03 Thread db
On 3 Oct 2017, at 22:19, Ryan Schmidt wrote: > Once we get automatic distfile mirroring back online it will be a nonissue. Any date? In any case, please do announce it in the lists.

Re: curl error:1407742E:SSL

2017-10-03 Thread db
On 3 Oct 2017, at 17:30, Ken Cunningham wrote: > Please see You could add it to https://guide.macports.org/#installing.macports.source . Is it safe to just recompile MP overwriting the package installation?

Re: curl error:1407742E:SSL

2017-10-03 Thread db
On 3 Oct 2017, at 17:30, Ken Cunningham wrote: > Please see No option in config file to avoid recompiling MP? I was thinking about symlinking to MP's version as a last resort.

curl error:1407742E:SSL

2017-10-03 Thread db
I'm getting the error below when fetching from pypi. Can I force use of MP's curl instead of OS X (10.8)'s? ---> Attempting to fetch cffi-1.11.0.tar.gz from https://distfiles.macports.org/py-cffi DEBUG: Fetching distfile failed: The requested URL returned error: 404 ---> Attempting to fetch

Re: Uninstall a port and ONLY THAT PORT's dependencies?

2017-10-02 Thread db
On 2 Oct 2017, at 15:56, Carlo Tambuatco wrote: > Is —follow-dependencies smart enough to uninstall dep(A), but not dep(A,B,C)…? From port's man page: To uninstall portname and then recursively uninstall all ports it depended on, use --follow-dependencies. This will not

Re: Uninstall a port and ONLY THAT PORT's dependencies?

2017-10-01 Thread db
On 1 Oct 2017, at 18:57, Ryan Schmidt wrote: > On Oct 1, 2017, at 05:50, Carlo Tambuatco wrote: >> Is there a way to uninstall a port and only those ports that are >> dependencies of just that port? >> So I want to uninstall port A and dependencies of A: dep(A) but not

Re: xcode, clt or both

2017-09-20 Thread db
On 19 Sep 2017, at 23:06, Ryan Schmidt <ryandes...@macports.org> wrote: > On Sep 19, 2017, at 11:40, db wrote: >> On 19 Sep 2017, at 01:01, Ryan Schmidt wrote: >>> For certain subsets of ports, you can get by with installing just one or >>> the other. >>

Re: xcode, clt or both

2017-09-19 Thread db
On 19 Sep 2017, at 01:01, Ryan Schmidt wrote: > For certain subsets of ports, you can get by with installing just one or the > other. How can I know this beforehand? That's the reason I'm actually asking what exactly MP needs Xcode, CLT or both for. For example, if a

Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion

2017-09-14 Thread db
On 14 Sep 2017, at 13:25, Ian Wadham <iandw...@gmail.com> wrote: > On 14/09/2017, at 7:57 PM, db wrote: >> In case you have Time Machine or a clone, just restore /opt/local/ and >> /Applications/MacPorts/. > Heh, heh! Someone else suggested that and it was also one

Re: Searching macports-users Archives

2017-09-04 Thread db
On 4 Sep 2017, at 15:46, Craig Treleaven wrote: > http://www.mail-archive.com/macports-users@lists.macosforge.org/ http://www.mail-archive.com/macports-users@lists.macports.org/maillist.html

Re: running macports along with homebrew

2017-09-02 Thread db
On 2 Sep 2017, at 01:06, Ryan Schmidt <ryandes...@macports.org> wrote: >> On Sep 1, 2017, at 03:22, db <iams...@gmail.com> wrote: >> On 31 Aug 2017, at 21:34, Craig Treleaven <ctrelea...@macports.org> wrote: >>> Gentle reminders, regularily applied, tend to c

Re: running macports along with homebrew

2017-09-01 Thread db
On 31 Aug 2017, at 21:34, Craig Treleaven wrote: > Gentle reminders, regularily applied, tend to cure the ‘missing ports and > updated versions’ issue. It shouldn't work like that. Actually, it didn't. > I understand the attraction to having a command line way to check

Re: running macports along with homebrew

2017-09-01 Thread db
On 31 Aug 2017, at 21:46, Daniel J. Luke wrote: > Indeed, a quick look at pacakges.macports.org indicates there are 22,957 > binary archives available. As of now 19944 ports. No vagrant, no stem — yet.

Re: running macports along with homebrew

2017-08-31 Thread db
On 31 Aug 2017, at 17:53, Ken Cunningham wrote: > I think homebrew gets attention for two reasons. > > > 1. a one-line copy & paste install command that is pasted into the terminal > (macports could / should do that too, BTW). > > 2. the fact that it

Re: running macports along with homebrew

2017-08-31 Thread db
On 31 Aug 2017, at 15:35, Craig Treleaven wrote: > What is it that you want that MacPorts does not provide? As I said in my OP, missing ports and updated versions, cask...

Re: running macports along with homebrew

2017-08-31 Thread db
On 30 Aug 2017, at 10:16, Richard L. Hamilton wrote: > the newer, safer convention is distinct subdirectories of /opt, for each > package or set of commonly managed packages; thus, MacPorts by default uses > /opt/local, XQuartz uses /opt/X11 (for the stuff that's not

Re: running macports along with homebrew

2017-08-29 Thread db
On 29 Aug 2017, at 23:39, Mojca Miklavec wrote: > But most important: in case you do end up with two systems, make sure to > quadruple check before submitting any bug reports to make sure that the error > is not due to the packages intermixed with each other.

Re: running macports along with homebrew

2017-08-29 Thread db
On 29 Aug 2017, at 23:24, Ryan Schmidt wrote: > The best practice is not to do that. We don't support it. It can cause you > problems that we don't want to spend time investigating, because they > wouldn't be problems if you hadn't also used a second package manager.

Re: running macports along with homebrew

2017-08-29 Thread db
On 29 Aug 2017, at 19:27, Ken Cunningham wrote: > FYI, it's actually not hard to write a portfile to install a binary, and it's > useful in some cases. Yes, but cask already has 3.7K. Convenient, isn't it? > But MacPorts so far has explicitly stated they are

Re: running macports along with homebrew

2017-08-29 Thread db
On 29 Aug 2017, at 14:55, Umesh Singla wrote: > /opt/local/bin:/opt/local/sbin:/usr/local/gradle/gradle-2.11/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin > > It simply looks for the packages in the default macports directory > (/opt/local) first and then

running macports along with homebrew

2017-08-29 Thread db
I searched the docs, the list's archive and stackexchange amongst other sources for sort of a best practice for running macports along with homebrew, to no avail. From those I gathered that the only problem one could run into, it seems, would be at build time — hence some advise on changing

Re: Anyone successfully install "meld"? Failed on gstreamer1-gst-plugins-bad

2017-08-16 Thread db
On 16 Aug 2017, at 14:12, James Kulp wrote: > Thanks all for the help. After a selfupdate, gstreamer1-gst-plugins-bad > installed ok, and the rest of the dependencies from "meld" also were fine, > and "meld" is good. Can anyone take a look at #51512 (3.16.0)? Alternatively,

Re: macports' hardlinks and time machine backups

2017-08-14 Thread db
On 14 Aug 2017, at 14:16, Rainer Müller wrote: > Finder on macOS uses base 10 Thanks. Somehow I thought it had been reverted without ever verifying. Oh well…

Re: macports' hardlinks and time machine backups

2017-08-13 Thread db
On 13 Aug 2017, at 18:46, Clemens Lang wrote: > MacPorts no longer uses hardlinks. We now keep the pristine state in archives > in /opt/local/var/macports/software instead of hardlinking everything from > there. Not even for other parts that I'm not aware of, that would

macports' hardlinks and time machine backups

2017-08-13 Thread db
I perchance stumbled upon this post [1] and couldn't find what's the actual state. In my system du reports ~8.8G for my prefix while Finder ~9.4. What's changed from then? [1] https://lists.macports.org/pipermail/macports-dev/2010-May/011938.html

Re: Anyone successfully install "meld"? Failed on gstreamer1-gst-plugins-bad

2017-08-12 Thread db
It's good to know that meld is on macports. In trac, there's a patch at https://trac.macports.org/ticket/51512 for 3.16.0, which you might want to give a try.

Re: python36 uninstall problem

2017-07-18 Thread db
On 18 Jul 2017, at 16:16, Ray Zimmerman wrote: > However, I notice there is still a 105 MB directory at … > /opt/local/Library/Frameworks/Python.framework/Versions/3.6 What's the output for this command? port provides

Re: nmap doesn't like libc++ ?

2017-07-13 Thread db
On 12 Jul 2017, at 22:42, Ryan Schmidt wrote: > On Jul 12, 2017, at 14:27, Ken Cunningham wrote: > You could do this in the portfile: >> configure.cxxflags-append -stdlib=libc++ >> configure.ldflags-append -stdlib=libc++ >> and your build should proceed through. Should.

Re: get portfiles from all sources

2017-07-03 Thread db
On 3 Jul 2017, at 18:02, Rainer Müller wrote: > I would consider this a bug in 'port search', as libsdl2 as a port argument > will always refer to the first one, so it does not make sense to print > additional results. Couldn't the pseudo-portname `all` do what the

Re: get portfiles from all sources

2017-07-03 Thread db
On 3 Jul 2017, at 13:45, Rainer Müller wrote: > You can only use the Portfile from the first ports tree providing a port with > that name. I though that `all` should get it from all trees, according to port's man page The pseudo-portnames are: o all: all the

get portfiles from all sources

2017-07-03 Thread db
I don't seem to find a way to get all portfiles from sources listed in sources.conf. In my case: file:///opt/local/myports file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ [default] #rsync://rsync.macports.org/release/tarballs/ports.tar [default] I thought this should

Re: logging all port command activity

2017-06-29 Thread db
On 29 Jun 2017, at 02:47, Ryan Schmidt wrote: > There's no such capability built in. Would implementing such a feature be feasible (and worth filing a ticket)?

Re: replace existing attachment of the same name in trac

2017-06-26 Thread db
On 26 Jun 2017, at 21:06, Ryan Schmidt wrote: > I hadn't noticed. If it does that, it would probably be a Trac bug. If anyone confirms it, I leave it to him to file.

Re: Mac port error

2017-06-22 Thread db
> I would like to ask also if the mac port platform could be used as a virtual > computer with the Lnux shell on it. If I guess what you mean — use xhyve (http://www.pagetable.com/?p=831) or qemu.

Re: Missing /opt/local/share/man/whatis DB

2017-06-22 Thread db
On 22 Jun 2017, at 05:09, Richard L. Hamilton wrote: > And ideally, anything that installs (or removes) man pages from a man page > directory should, after installing (or removing) the pages, run makewhatis, > e.g. > > /usr/libexec/makewhatis /opt/local/'share/man If you

  1   2   >