Re: How to get date when port was added? To list ports added in last 1/2/3/.../X weeks?

On 19 Jun 2017, at 23:19, Kurt Pfeifle via macports-users wrote: > Though to determine what has changed in an existing (and known to me) > repository since a date is a useful feature too -- my curiosity right now is > itching about how to learn about

Re: libxml2 2.9.4 config error #54070 wontfix

On 31 May 2017, at 15:16, Daniel J. Luke wrote: > yes, but base doesn't currently know that it should do that (this thread > contains some suggestions about how that might be possible). I meant doing this from within base for the handful of utilities they are — no prio

Re: libxml2 2.9.4 config error #54070 wontfix

On 30 May 2017, at 17:08, Ryan Schmidt wrote: > The problem is that configure scripts of ports like the one you're building > automatically look for gawk and other similar utilities. Even if the system > version of awk would work, they prefer the MacPorts gawk if it's

Re: libxml2 2.9.4 config error #54070 wontfix

On 30 May 2017, at 14:58, Ryan Schmidt wrote: > What specific fix to you recommend? I have no fix to recommend. My uneducated guess is that it's searching for /opt/local/lib/libreadline.6.dylib while I've just updated it to v7. Would that be non-fixable?

libxml2 2.9.4 config error #54070 wontfix

I got basically the same error referenced in that ticket. :info:configure config.status: creating libxml2.spec :info:configure dyld: Library not loaded: /opt/local/lib/libreadline.6.dylib :info:configure Referenced from: /opt/local/bin/gawk :info:configure Reason: image not found

Re: how to uninstall macport with OS conflict ?

On 19 May 2017, at 00:00, Clemens Lang wrote: > Run the MacPorts installer for your new OS (yes, I know it's > counter-intuitive), then follow the uninstall instructions. It should only > take a couple of minutes if you use the installer and allow for clean removal > even if

py-pyqt5 and qt56

How can I install py-pyqt5 with an older version of qt5? There are subports for python but not for qt. $ sudo port install py-pyqt5 Password: ---> Computing dependencies for py-pyqt5 Error: Can't install qt5-qtscript because conflicting ports are active: qt56-qtbase Error: Follow

python36 and readline

python36 with py36-readline installed results in a crash https://trac.macports.org/ticket/48807#comment:100 python36 +readline seems to work though. Any ideas?

Re: 'port definitions old' even after git pull

On 26 Apr 2017, at 09:26, Jan Stary wrote: > Am I missing something obvious? Did you run `sudo port -v sync` as per https://trac.macports.org/wiki/howto/SyncingWithGit?

Re: qt5 build dependency on clang

On 25 Apr 2017, at 18:59, Ken Cunningham wrote: > Do I misunderstand? No, exactly so.

Re: qt5 build dependency on clang

On 22 Apr 2017, at 23:05, Ken Cunningham wrote: > because cxx_stdlib will equal libc++ and therefore this test (which would > lead to the code that does the whitelisting) will fail. Bear with me — what I actually had in mind was, since we have

Re: binutils warning

On 24 Apr 2017, at 21:24, Ryan Schmidt <ryandes...@macports.org> wrote: >> On Apr 24, 2017, at 14:22, db <iams...@gmail.com> wrote: >> #22539 atlas (also #22674) -> it built for hours and I didn't let it >> finish, sorry > Yes atlas takes hours to buil

Re: binutils warning

On 22 Apr 2017, at 20:21, Ryan Schmidt wrote: > Feel free to re-test the ports that failed to build back then that caused us > to add that warning. #22539 atlas (also #22674) -> it built for hours and I didn't let it finish, sorry #22679 wine-crossover-games ->

Re: qt5 build dependency on clang

On 22 Apr 2017, at 21:58, Ryan Schmidt wrote: > Sounds plausible. What's your question / problem with this? Ken already point me to cxx11-1.1.tcl, but I still don't get why 4.0 isn't whitelisted in a system whose default is set to 3.9.

Re: qt5 build dependency on clang

On 22 Apr 2017, at 21:27, Ken Cunningham wrote: > For your other situation where the cxx_stdlib has been set to libc++, this > whitelisting will not be forced Why not? I'm missing something.

qt5 build dependency on clang

On a 10.8.5-system with default compiler qt5 @5.7.1 and qt56 @5.6.2 require clang-4.0 to build, while another whose compiler is set to clang-3.9 shows this as dependency. Can anyone confirm the former?

binutils warning

I thought of upgrading strings and found it in binutils. During installation a warning showed which doesn't seem to hold true at least from inspecting the contents tracked by port command, and the notes advise to uninstall it. It has no maintainer. Any ideas? [test/Desktop] > install binutils

Re: fullscreen multiwindow OS X bug?

On 20 Apr 2017, at 19:21, René J.V. Bertin wrote: > I ran into what looks to be a bug in Apple's fullscreen algorithms. On 10.9.5 > with screens DO NOT have separate spaces: > ... > Same happens with a Qt-based console emulator so this is not a bug in > Terminal.app . I

Re: building from source with libc++

On 20 Apr 2017, at 22:54, Ken Cunningham wrote: > You’ve made clang-3.9 a build dep for everything by setting the default > compiler to clang-3.9. It will always be listed, for all ports. I often check dependencies and sizes with a couple of functions and these

Re: building from source with libc++

On 20 Apr 2017, at 20:06, Ken Cunningham <ken.cunningham.web...@gmail.com> wrote: > On 2017-04-20, at 10:42 AM, db wrote: >> Could you please tell me if you see the warning I mentionend and the >> following line in every `port info` result? >> Build Dependencies:

Re: building from source with libc++

On 20 Apr 2017, at 19:01, Ken Cunningham wrote: > Now to be fair, IF you get a build problem, there are increased expectations > on you to check into it before you file a ticket about it. Specifically, try > to build it with a stock clang compiler and see if

Re: building from source with libc++

On 20 Apr 2017, at 00:13, Ken Cunningham wrote: > I think the Lion and Mountain Lion LibCxxOnOlderSystems instructions could > probably suggest/recommend installing and setting the default compiler to > something newer, but I defer to the gurus here. After

Re: building from source with libc++

On 19 Apr 2017, at 18:22, Ken Cunningham wrote: > You're right, that option is not listed there. It is listed in the > LibCxxOnOlderSystems instructions, which is where I originally found it. > It looks like this, in macports.conf on my system. >

Re: building from source with libc++

On 19 Apr 2017, at 10:59, Chris Jones wrote: > You cannot really compare the stock LLVM/Clang releases to the Apple versions. I read https://trac.macports.org/wiki/UsingTheRightCompiler and this comment from Rainer, I guess, https://superuser.com/a/130474 and thus I'm

Re: building from source with libc++

On 19 Apr 2017, at 10:13, Mojca Miklavec wrote: > https://trac.macports.org/wiki/XcodeVersionInfo That doesn't tell me anything different from the output I posted. I still don't exactly know which clang version I have. > You would run into problems if you

Re: building from source with libc++

Thanks Ken for the detailed post. On 18 Apr 2017, at 17:45, Ken Cunningham wrote: > There are two issues: > 1. cxx11 features required. > ... > Although you could say the Portfiles should all be updated as this is > recognized, it is in the end MUCH easier to

port leaf becoming requested

I wanted to install texinfo which is actually a leaf of coreutils, but `sudo port install texinfo` doesn't make it a requested port, as I would expect. Is it intended behaviour? I suppose, I could either uninstall leaves and reinstall it, or use setrequested.

Re: building from source with libc++

I filed #53994, #53995, #53996 for highlight, nmap and ostinato respectively, failing to build with libc++. I'd appreciate if anyone could peek at the logs and recognize a pattern or tell these are unrelated.

Re: port-depgraph warning

On 14 Apr 2017, at 01:59, Ryan Schmidt wrote: > Sure. That's still valid. There haven't been any changes in port-depgraph > since we moved to GitHub so there's no particular advantage to switching the > portfile to GitHub yet. I think the tcl script should be in base,

Re: port-depgraph warning

On 13 Apr 2017, at 17:38, Rainer Müller wrote: > You are effectively running it with an empty argument, which is not a valid > port name: > $ port-depgraph "" > That could indeed be handled more graceful. The source can be found here > after the move to GitHub: >

Re: notes repeatedly showing in port session

On 12 Apr 2017, at 16:21, Ryan Schmidt wrote: > If you want to get this fix right now, before the next version of MacPorts is > released, the official way would be to check out the master of the repository > and build the whole thing from source. Oh well…from what I

Re: port-depgraph warning

On 11 Apr 2017, at 22:36, db <iams...@gmail.com> wrote: > Without arguments shows this warning > > $ port-depgraph > Warning: It looks like your PortIndex file for file:///opt/local/myports may > be corrupt. > Warning: It looks like your PortIndex file for > fil

Re: notes repeatedly showing in port session

On 12 Apr 2017, at 11:02, db <iams...@gmail.com> wrote: > On 12 Apr 2017, at 01:19, Ryan Schmidt <ryandes...@macports.org> wrote: >> That sounds like a bug. We probably didn't test the change with shell mode. > #53967, I hope I filed it correctly. That was quickly fixed

Re: notes repeatedly showing in port session

On 12 Apr 2017, at 01:19, Ryan Schmidt wrote: > That sounds like a bug. We probably didn't test the change with shell mode. #53967, I hope I filed it correctly.

port-depgraph warning

Without arguments shows this warning $ port-depgraph Warning: It looks like your PortIndex file for file:///opt/local/myports may be corrupt. Warning: It looks like your PortIndex file for file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ may be corrupt. Error: :

notes repeatedly showing in port session

After installing a port with notes, these show after every command during the same shell mode session on port 2.4.1. Is there any way to disable this great feature?

Re: JPortsUI has been updated

oaded from > https://sourceforge.net/projects/jportsui/files/ > > Feel free to submit a ticket or feature request with SourceForge's > "Tickets" navigation button or directly gmail me. Special thanks for > help from Manfred Antar and db-iamsudo!

Re: Pallet requires Tcl directory

On 11 Apr 2017, at 04:13, Ryan Schmidt wrote: > Ok. I don't see anything in the crash report that says to me that 10.8 is > unsupported. I just see a crash, which someone needs to investigate and fix. Should I add it to an existing ticket or open a new one or do

qt5 fails to build

On 10.8.5. I don't know if #52922 is related. Should I open a ticket? Here's the log shortened to its last lines :info:build /opt/local/bin/clang++-mp-4.0 -c -pipe -arch x86_64 -stdlib=macports-libstdc++ -isysroot

Re: MP_EDITOR doesn't work

On 6 Apr 2017, at 02:35, Ryan Schmidt wrote: > export EDITOR=editor.sh And does it work with MP_EDITOR? I just tried setting it in a vanilla vm, no dice. I set -dv when editing a portfile, but no related information is being logged.

Re: MP_EDITOR doesn't work

On 4 Apr 2017, at 11:21, db <iams...@gmail.com> wrote: > On 4 Apr 2017, at 11:18, Rainer Müller <rai...@macports.org> wrote: >> How did you test this? This works fine for me: >> $ export MP_EDITOR=less >> $ port edit zlib > export VISUAL=/opt/local/bin/vim

Re: Difficulty in upgrading MacPorts from El Capitan to Sierra

On 4 Apr 2017, at 09:44, Barrie Stott wrote: > 2. I would like to be able to take a requested port and find the tree of > ports that would need to be installed before this port. http://apple.stackexchange.com/questions/26921/installed-macports-packages-sizes/240638#240638

Re: MP_EDITOR doesn't work

On 4 Apr 2017, at 11:18, Rainer Müller wrote: > How did you test this? This works fine for me: > $ export MP_EDITOR=less > $ port edit zlib export VISUAL=/opt/local/bin/vim works export MP_EDITOR=/opt/local/bin/vim doesn't

MP_EDITOR doesn't work

I set MP_EDITOR but it doesn't seem to work on base 2.4.1. VISUAL, second var MP checks according to the guide, does though.

Re: building from source with libc++

On 3 Apr 2017, at 18:09, Mojca Miklavec wrote: > Basically yes. You could follow point 3 of > https://trac.macports.org/wiki/Migration Is the script from 3.e. relevant if no particular variants were installed? I ask because I probably won't automate the whole process as I

Re: building from source with libc++

On 28 Mar 2017, at 13:15, Rainer Müller wrote: > The support in base is missing to differentiate between binary archives > with a different cxx_stdlib. That is required to provide an upgrade path > for existing installations. May I assume that that won't happen in the

Re: building from source with libc++

On 27 Mar 2017, at 11:12, Mojca Miklavec wrote: > Dealbreaker: >https://trac.macports.org/ticket/50448 Thanks for pointing that out. I skimmed through it. What's the actual state re libc++ binaries for <10.9? Is dropping support for <10.9 something MP team is

Re: building from source with libc++

On 24 Mar 2017, at 22:24, Ryan Schmidt wrote: >> Should I expect to encounter problems when switching to building from source >> with libc++ for the same ports whose binaries work fine with libstdc++? > > Certainly; libc++ on 10.8 is a nonstandard configuration that

Re: building from source with libc++

ith the C++ > library chosen. > > Please do open a ticket with whatever relevant data you can provide. > >> On Mar 24, 2017, at 14:24, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> >> On Mar 24, 2017, at 14:48, db <iams...@gmail.com> wrote

Re: building from source with libc++

On 24 Mar 2017, at 19:21, Ryan Schmidt wrote: > Upgrading to a version of macOS with libc++ as default (10.9 and later) will > probably make your MacPorts life easier, but it's up to you of course. Despite the overall lower quality and usability of 10.9+, I don't see

Re: building from source with libc++

On 24 Mar 2017, at 16:00, Rainer Müller wrote: > A similar ticket had been filed before: > https://trac.macports.org/ticket/52335 I don't see how that explains that 1.6.4_0 in one system is the binary from MP, but this same version fails to compile in another identical

Re: fail to destroot port with only makefile

On 8 Mar 2017, at 01:10, Ryan Schmidt wrote: >> On 7 Mar 2017, at 20:00, Ryan Schmidt wrote: >>> That can be an acceptable workaround. Sometimes it has side effects. I >>> don't know if it does with this port. > > In the destroot phase, you should not be attempting to

Re: fail to destroot port with only makefile

On 7 Mar 2017, at 20:00, Ryan Schmidt wrote: > That can be an acceptable workaround. Sometimes it has side effects. I don't > know if it does with this port. Can you give an example? Something strange I found is that file copy fails silently, no log whatsoever, pre-

fail to destroot port with only makefile

I'm trying to port a client that comes with only a makefile, but fail to destroot it, although it sort of does if I sudo manually. I attach the log. https://github.com/tldr-pages/tldr-cpp-client/blob/master/Makefile main.log Description: Binary data

Re: verbose output in shell mode

I would expect some output without verbose flag like $ port livecheck [port] [port] seems to be up to date Not worth a feature request, I guess. On 6 Mar 2017, at 15:05, Ryan Schmidt <ryandes...@macports.org> wrote: > On Mar 6, 2017, at 08:03, db <iams...@gmail.com> wrote: >

Re: verbose output in shell mode

I meant try with other ports, e.g., emacs $ port livecheck emacs $ $ port -v livecheck emacs emacs seems to be up to date Not all ports give the same output with livecheck without -v. On 6 Mar 2017, at 14:54, Ryan Schmidt <ryandes...@macports.org> wrote: > On Mar 6, 2017, at 07:53,

Re: verbose output in shell mode

Try with emacs. On 6 Mar 2017, at 14:47, Ryan Schmidt <ryandes...@macports.org> wrote: > On Mar 6, 2017, at 07:44, db wrote: > >> Do you know of any means that I'm not aware of to make livecheck output its >> result without -v? > > > There doesn't seem

Re: verbose output in shell mode

Do you know of any means that I'm not aware of to make livecheck output its result without -v? On 6 Mar 2017, at 13:45, Ryan Schmidt <ryandes...@macports.org> wrote: > >> On Mar 6, 2017, at 03:46, db <iams...@gmail.com> wrote: >> >> Is there any way to enabl

Re: Migration Assistant moved MacPorts home directories

On 2 Mar 2017, at 01:21, Brandon Allbery wrote: > In fact only one change is needed: you do some of the early steps on the > origin system instead of all of it on the destination. I've used an adjusted > version of that a few times to do migrations, including with Apple's

#53591 terminal_markdown_viewer @1.6.3 : Styled Terminal Markdown Viewer

I submitted this one about a week ago.

Re: set port not to upgrade

rts would be a reasonable excuse for using it more often. What's your experience with it and MacPorts? Could you mention any caveats for a use case like the above? On 17 Feb 2017, at 21:54, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Feb 17, 2017, at 10:13, db wrote: &

Re: set port not to upgrade

> >>> On Feb 14, 2017, at 8:15 AM, Carlo Tambuatco <oraclmas...@gmail.com> wrote: >>> >>> You can try sudo port upgrade outdated and not >>> >>> or >>> >>> sudo port upgrade outdated and not and not rdependentof: >&

set port not to upgrade

How can I mark a port to not be upgraded by `port upgrade outdated`, for example, one that has a bug in my system version?

README vs installed documentation

Sometimes the README files from tarballs is better (re completeness/clarity) than the installed documentation. Is there any way to include them by default?

new ports not showing in search

Could you tell when a new port is listed at macports.org? E.g., hstr has already been accepted but it doesn't show up. https://www.macports.org/ports.php?by=name=hstr

Re: override local port

On 6 Feb 2017, at 02:57, Ryan Schmidt wrote: > If you are using a git checkout of the complete ports tree (like I am), then > you have no use for the rsync tarball anymore. Not yet, but I might give it a try. Any caveats worth mentioning or adding to the guide?

Re: override local port

, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > Hi, > > On 02/02/17 16:16, db wrote: >> On 2 Feb 2017, at 16:34, Mojca Miklavec <mo...@macports.org> wrote: >>> If you only want to do it once, you can cd to the folder with the port >>> that

Re: override local port

On 2 Feb 2017, at 16:34, Mojca Miklavec wrote: > If you only want to do it once, you can cd to the folder with the port > that you want to use and run "sudo port ..." from there. Hmm…no, I thought I could mark the ports' default priority/availability, something like

Re: override local port

I already have a local repo — I'd like a port in the rsync tree to exceptionally override the local one (higher preference) while keeping both in place. On 2 Feb 2017, at 14:31, Mojca Miklavec <mo...@macports.org> wrote: > On 2 February 2017 at 09:17, db wrote: >> How can I o

override local port

How can I override a local portfile without deleting it? I want to keep some ports locally, for example, after I submitted a new, locally tested port that made it in the repo, or when I want to keep an older portfile until I fully tested the latest version of an application.

Re: Help wanted: unbuffer, or stdbuf

Both should be there port contents coreutils | grep stdb # bins are prefixed with g port contents expect | grep unbuffer On 31 Jan 2017, at 05:27, Michael wrote: > So I wanted to linebuffer a program that is feeding into a pipe. > > Looking around with Google, I found two

Re: Help wanted: unbuffer, or stdbuf

On 31 Jan 2017, at 06:47, Michael wrote: > Nope, /usr/bin. Which package installs script? util-linux

older lib for port

Is it feasible to maintain an older lib to compile a certain port? I wanted to update ngrep 1.45 (sourceforge) to 1.46 (github) and tried compiling in a system that had an older version of libpcap, 1.7.4 (current is 1.8.1). It worked only without the patches. It's far from ideal, but it has no

<    1   2