On Jun 19, 2018, at 21:05, Lenore Horner wrote:
> On Jun 11, 2018, at 17:57, Lenore Horner wrote:
>
>> gnucash is saying
>> Dynamic session lookup supported but failed: launchd did not provide a
>> socket path, verify that org.freedesktop.dbus-session.plist is loaded!
>>
>> but when I try to
On Jun 18, 2018, at 16:15, Carlo Tambuatco wrote:
> Doing some routine cleaning up of old unecessary ports and I was wondering
> how port treats duplicate ports... I realised I've got two instances of the
> xrender port installed so I'll use this as an example.
>
> I've got these two ports
On Jun 16, 2018, at 17:01, Michael wrote:
> Let's say I have a bunch of scripts that start with #!/usr/bin/perl
>
> There is a python_select,but not a perl_select.
>
> How do I avoid the out of date system Perl, which doesn't have the needed
> support modules, and installing those modules
On Jun 16, 2018, at 19:12, Rainer Müller wrote:
> On 2018-06-17 01:47, Michael wrote:
>> How do I force port to compile a port when I have a local port file?
>>
>> If I say "port build git", it will build with my local port file, and local
>> patches.
>>
>> Unfortunately, I cannot figure out
On Jun 16, 2018, at 18:13, Michael wrote:
> On 2018-06-16, at 3:51 PM, Michael wrote:
>
>> I'm trying to use a local port file, and it's not working. What am I doing
>> wrong?
>>
>> bash-3.2# cat /opt/local/etc/macports/sources.conf
>> # $Id: sources.conf 106803 2013-06-08 16:22:39Z
On Jun 16, 2018, at 17:51, Michael wrote:
> rsync://rsync.macports.org/release/tarballs/ports.tar [default]
It's unrelated to the issue you're reporting, but that URL is deprecated; you
should change it to:
rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
On Jun 17, 2018, at 11:52, Dave Horsfall wrote:
> ---> Uninstalling sqlite3 @3.23.1_0+universal
> ---> Cleaning sqlite3
> You haven't run 'sudo port reclaim' in two weeks. It's recommended you run
> this regularly to reclaim disk space. Would you like to run it now? [Y/n]:y
> ---> Checking
On Jun 16, 2018, at 16:02, Kevin Reid wrote:
> I just ran a selfupdate and it prompted me to run reclaim and during the
> reclaim process produced this error.
>
> ---> Updating MacPorts base sources using rsync
> MacPorts base version 2.4.3 installed,
> MacPorts base version 2.5.2
On Jun 14, 2018, at 12:58, Langer, Stephen A. (Fed) wrote:
> Thanks for the advice. If I make a new non-standardly located macports
> directory on my system, build my program and all of its dependencies in that
> directory (including dependencies that aren't packaged with macports), and
>
On Jun 10, 2018, at 23:05, Dave Horsfall wrote:
> Sanitised version attached; it's a bit out of date, but the hardware has not
> changed.
>
> I'll attempt another High Sierra upgrade later, when I have a few hours to
> spare, and report back.
>
> -- Dave
Ok, so you have the MacBook6,1.
On Jun 10, 2018, at 23:39, Dave Horsfall wrote:
> On Sun, 10 Jun 2018, Ken Cunningham wrote:
>
>> Dave, I would be tempted to uninstall gcc49 and just see what happens. I
>> don't think you need it.
>
> OK, with trepidation:
>
>ozzie:~ dave# port uninstall gcc49
>---> Deactivating
On Jun 5, 2018, at 11:42, Dave Horsfall wrote:
> Speaking of Xcode, I keep being offered to upgrade it, but it will only run
> on High Sierra.
I assume this upgrade offer is coming from the Mac App Store. I'm not sure why
it would offer you a version of Xcode that's not compatible with your
On Jun 4, 2018, at 16:05, Dave Horsfall wrote:
> On Mon, 4 Jun 2018, Ryan Schmidt wrote:
>
>>> I won't include the entire log (yet), as I'm sure that I'm not the only
>>> one. What I certainly do *not* want, however, is to rebuild GCC, so I
>>> consider
On Jun 4, 2018, at 03:42, Mojca Miklavec wrote:
> On 4 June 2018 at 05:36, Dave Horsfall wrote:
>> ---> Building gcc49
>> Error: Failed to build gcc49: command execution failed
>> Error: See
>>
On Jun 3, 2018, at 22:36, Dave Horsfall wrote:
> ---> Building gcc49
> Error: Failed to build gcc49: command execution failed
> Error: See
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/main.log
> for
On Jun 2, 2018, at 08:46, FritzS - gmx wrote:
> Am 02.06.2018 um 15:34 schrieb Rainer Müller:
>
>> On 2018-06-02 10:00, FritzS - gmx wrote:
>>> Whats are the differences between this two packages of GIMP?
>>>
>>> Make this version an GIMP.app?
>>>
On Jun 1, 2018, at 22:11, Eitan Adler wrote:
> On 1 June 2018 at 02:14, Rainer Müller wrote:
>> On 1 June 2018 02:35:35 GMT+02:00, Eitan Adler wrote:
>>> Is it possible to get debug symbols enabled by default for ports? I'd
>>> like to always compile c-alike languages with "-g" and not have them
On May 31, 2018, at 21:50, Eitan Adler wrote:
> On 31 May 2018 at 19:45, Ryan Schmidt wrote:
>>
>> On May 31, 2018, at 21:42, Eitan Adler wrote:
>>> On 31 May 2018 at 19:40, Ryan Schmidt wrote:
>>>> Or: A setting in macports.conf that makes MacPorts base ad
On May 31, 2018, at 21:42, Eitan Adler wrote:
> On 31 May 2018 at 19:40, Ryan Schmidt wrote:
>> Or: A setting in macports.conf that makes MacPorts base add -g for all
>> ports? That would cause the built result to be different. We could offer
>> that, but would h
On May 31, 2018, at 21:10, Eitan Adler wrote:
> On Thursday, 31 May 2018, Ken Cunningham wrote:
>> Well, to do that, you would have to change the default configure.optflags in
>> portconfigure.tcl
>>
>> open
>>
>> /opt/local/libexec/macports/lib/port1.0/portconfigure.tcl
>>
>> and change
On May 31, 2018, at 17:40, Daniel Wilks wrote:
>
> Thanks. I’ve already updated the Portfile and am installing the symlinks as
> files which is working. It just pointed out to me that I have no idea how to
> install a symlink.
I haven't attempted to do this update yet, so I'm looking forward
On May 31, 2018, at 08:04, Lee Bast wrote:
> Hello all,
> Before I dive into this any farther I'm curious if anyone else has
> noticed something or if it's specific to me. Across 3 different machines (2
> MPs and an rMBP) running a mix of 10.12.6 and 10.13.4 I did a standard
>
On May 29, 2018, at 08:58, Rainer Müller wrote:
> On 2018-05-29 06:24, Shuvayan wrote:
>
>>> On 29-May-2018, at 9:47 AM, Shuvayan wrote:
>>>
>>> Output:DEBUG: Copying
>>> /Users/shuvayan/Library/Preferences/com.apple.dt.Xcode.plist to
>>> /opt/local/var/macports/home/Library/Preferences
>>>
On May 26, 2018, at 14:38, Ken Cunningham wrote:
> On May 26, 2018, at 12:27 PM, Ryan Schmidt wrote:
>
>> The error occurs when there is a mismatch between which C++ standard library
>> a port says it uses (by setting configure.cxx_stdlib, or by leaving it set
>&
On May 26, 2018, at 14:25, Ken Cunningham wrote:
> On May 26, 2018, at 9:49 AM, Ryan Schmidt wrote:
>
>> On May 26, 2018, at 11:48, Ken Cunningham wrote:
>>
>>> Well I think you did the cmake finaggeling last time Not sure you could
>>> find a bette
On May 26, 2018, at 11:48, Ken Cunningham wrote:
> Well I think you did the cmake finaggeling last time Not sure you could
> find a better way, but I wait to see...
I don't recall what you're referring to.
On May 26, 2018, at 11:15, Ken Cunningham wrote:
> On May 25, 2018, at 12:05 PM, Ryan Schmidt wrote:
>
>> It's "broken" in that it links with libstdc++, even though MacPorts believes
>> it will link with libc++ on your system. The rev-upgrade code in previous
On Apr 18, 2018, at 23:42, Ryan Schmidt wrote:
> Thanks. I think this problem was introduced by a presumably unintentional
> part of this commit:
>
> https://github.com/macports/macports-ports/commit/e3710d6800e803ebaa9528d3bdb38fb2fcade513#diff-5513a677784c8c1520463fedf268a37f
On May 25, 2018, at 12:57, Zero King wrote:
> On Thu, May 17, 2018 at 11:36:39PM +1000, Joshua Root wrote:
>> It's been a week with no new tickets filed against base. I'll give it
>> one more week and then, if nothing comes up, tag a release candidate.
>>
>> - Josh
>
> I tried the rc1, and
On May 18, 2018, at 19:14, bunk3m wrote:
> I finally did the dist-upgrade to 2.4.4 on our iMac running 10.12.6
>
> While doing a upgrade outdated, libquicktime-devel hangs. So I can't update
> transcode. I see from the logs there are 404 not found errors.
The 404 errors relate to fetching a
On May 11, 2018, at 05:35, g5pw wrote:
> On 11 May 2018, at 09:56, Roy Henderson wrote:
>
>> With help from this list I think I have installed port Inkscape @0.92.3 but
>> when I launch the application the Help/About screen shows 0.92.2 with a date
>> of 2018-03-11.
>>
>> My next step is to
On May 13, 2018, at 19:02, Richard DeLaurell wrote:
> The port command N-switch (for non-interactive) doesn't seem to work in shell
> mode; is there an alternative?
It should work fine, to the extent that if you launch shell mode like this:
port -N
then the shell will not ask interactive
On May 13, 2018, at 02:25, david koloseni wrote:
> I have been installing octave on My machine Mac OS Siera, through Macports
> package manager but it installs octave 4.2.2 instead of octave 4.4.0. what is
> the problem? or what should I do to get Octave version 4.4.0?
File a ticket in the
On May 11, 2018, at 16:46, Ian Wadham wrote:
> I think KDE 4 apps are still installed without docs in MacPorts because of an
> intermittent
> build crash that could never get diagnosed and fixed.
Yup, it's still a problem.
https://trac.macports.org/ticket/53733#comment:4
On May 11, 2018, at 15:30, Ken Cunningham wrote:
> On 2018-05-11, at 12:52 PM, Ryan Schmidt wrote:
>
>> At least when Inkscape is installed with the +x11 variant, its Dock icon
>> will not function the way a normal Mac app's Dock icon would. Its icon will
>> bounc
On May 10, 2018, at 18:47, Roy Henderson wrote:
> However, when I try to launch it, Inkscape appears in the Dock bouncing so it
> obviously wants some attention but I can’t figure what …
At least when Inkscape is installed with the +x11 variant, its Dock icon will
not function the way a normal
On May 10, 2018, at 19:36, Roy Henderson wrote:
> Inkscape is 0.92.2 which is downlevel from the latest but perhaps MacPorts
> doesn’t yet have the absolute latest version.
MacPorts Inkscape was updated to 0.92.3 on April 17:
On May 8, 2018, at 15:10, Александр Искрижицкий wrote:
> I am new user of Mac and I need help.
Welcome!
> How I can install php7.2 with ZTS enabled? I need to work with pthreads
> extension.
We don't have php with zts at this time. See discussion of the problems with
that at
On May 2, 2018, at 21:41, Richard L. Hamilton wrote:
> Oddly enough, it builds fine on older e.g. El Capitan (I think even on Snow
> Leopard, but that box is slow, so I don't know yet).
>
> Will I have better luck using a different compiler, or does it just hate me?
> :-) I have 4.14.3_8
On Apr 29, 2018, at 11:33, Riccardo Mottola wrote:
> On 2018-04-29 14:36:02 +0200 Ken Cunningham wrote:
>
>> clang-3.4 will never work on PPC, so don't even bother.
>
> In the sense that it is too broken? It actually starts compiling.
In the sense that the clang developers have not added
On Apr 25, 2018, at 13:46, Riccardo Mottola wrote:
> I need it just as a dependency of gtk2. It is interesting that my last
> install (just 1 or 2 months ago) did not require it!
gtk2 requires gtk-doc. When gtk-doc was updated to version 1.28 last month,
dblatex was added as a dependency.
On Apr 25, 2018, at 03:46, Riccardo Mottola wrote:
> Then I resume upgrading.. and something pulls in texlive-bin
>
> ---> Computing dependencies for texlive-bin
> ---> Building texlive-bin
> Error: Failed to build texlive-bin: command execution failed
> Error: See
>
On Apr 22, 2018, at 23:59, Ulrich Wienands wrote:
> On Apr 22, 2018, at 10:18 PM, Ulrich Wienands wrote:
>
>> uli% sudo port -d selfupdate
>> Password:
>> DEBUG: Copying /Users/uli/Library/Preferences/com.apple.dt.Xcode.plist to
>> /opt/local/var/macports/home/Library/Preferences
>> DEBUG:
On Apr 20, 2018, at 09:14, petr.2006 wrote:
> I am trying to instal gollum in gem:
>
> sudo gem install gollum
> Building native extensions. This could take a while...
> ERROR: Error installing gollum:
> ERROR: Failed to build gem native extension.
>
>current directory:
>
On Apr 19, 2018, at 12:12, pagani laurent wrote:
> After totally cleaning my macports installation and reinstalling everything,
> I ended up having py27-jupyter and py36-jupyter installed :
>
> Macports>port -v installed py36-jupyter
> The following ports are currently installed:
>
On Apr 20, 2018, at 01:17, Riccardo wrote:
> while installing gimp dependencies, on Leopart 10.5 PPC
>
> ---> Building gdk-pixbuf2
> Error: Failed to build gdk-pixbuf2: command execution failed
> Error: See
>
On Apr 18, 2018, at 06:07, William H. Magillwrote:
> One assumes that a big problem with any migration guide (or automated
> process) will be with Apache and MAMP
>
> I haven’t run OSX Server for several years now, but the difference in
> locations between OSX Server’s locations (Site, etc.)
Thanks. I think this problem was introduced by a presumably unintentional part
of this commit:
https://github.com/macports/macports-ports/commit/e3710d6800e803ebaa9528d3bdb38fb2fcade513#diff-5513a677784c8c1520463fedf268a37f
I think that needs to be reverted, and the tk port's revision increased
On Apr 17, 2018, at 06:08, pagani laurent wrote:
> ---> Activating xorg-xproto @7.0.31_0
> Error: Failed to activate xorg-xproto: Image error:
> /opt/local/include/X11/X.h is being used by the active tk port. Please
> deactivate this port first, or use 'port -f activate xorg-xproto' to force
On Apr 16, 2018, at 15:50, Murray Eisenberg wrote:
> Error: Failed to fetch qrupdate: must set at least one Fortran variant
> (e.g. +gfortran, +gccX, +g95)
>
This message is printed by the compilers-1.0 portgroup, and is not customized
for the set of variants that a particular port offers:
On Apr 16, 2018, at 08:37, pagani laurent wrote:
> Here one such example :
>
> […]
> ---> Installing py36-six @1.11.0_0
> ---> Activating py36-six @1.11.0_0
> Error: Failed to activate py36-six: Image error:
>
Thanks for the pointers! The problem was that release/base was configured to
sync from the *old* location of trunk/base (from before I moved everything but
the rsync data onto the SSD):
git -C /Volumes/RAID/var/tmp/mprsyncup/release/base config remote.origin.url
/var/tmp/mprsyncup/trunk/base
I
On Apr 12, 2018, at 11:05, Chris Jones wrote:
> On 12/04/18 04:24, Ryan Schmidt wrote:
>> On Apr 11, 2018, at 21:54, Joshua Root wrote:
>>> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>>>
>>>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>>&g
On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>
> Can you remove the -q flag and/or retry running git fetch? That should give us
> an idea what went wrong here.
No change. No additional output is produced.
On Apr 11, 2018, at 21:54, Joshua Root wrote:
> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>
>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>
>>> No, rsync just hasn't updated yet. The ports are also a bit out of date.
>>> Ryan should be able to take a
On Apr 11, 2018, at 10:23, Joshua Root wrote:
> No, rsync just hasn't updated yet. The ports are also a bit out of date.
> Ryan should be able to take a look before too long.
mprsyncup is failing with:
2018-04-11T02:10:34+ error: pathspec 'v2.4.3' did not match any file(s)
known to git.
On Apr 7, 2018, at 15:13, Murray Eisenberg wrote:
> Would it be appropriate to open a ticket http://trac.macports.org?
No, since we were not involved in the creation of the openmodelica portfiles
nor do we host them in our repository, and we have no influence over those who
do host them to
On Apr 7, 2018, at 15:02, Ken Cunningham wrote:
> Also, installing both gcc5 and gcc7 and libgcc6 and libgcc just seems nutty,
> so I added gcc6 and gcc7 to the fortran variants — but that has nothing to do
> with the above.
Using both gcc5 and gcc7 in a single port would indeed be nutty, if
On Apr 7, 2018, at 13:56, Murray Eisenberg wrote:
> On 7 Apr2018, at 2:51 PM, Ryan Schmidt wrote:
>
>> On Apr 7, 2018, at 13:50, Murray Eisenberg wrote:
>>
>>> What’s happening now is befuddling to me. Doing the step
>>>
>>> echo rsync://build.
On Apr 7, 2018, at 13:50, Murray Eisenberg wrote:
> What’s happening now is befuddling to me. Doing the step
>
>echo rsync://build.openmodelica.org/macports/ >>
> /opt/local/etc/macports/sources.conf
>
> as root (sudo su - ) seems to have worked, as
>
On Apr 7, 2018, at 12:49, Ken Cunningham wrote:
> sounds like this software needs a port and a maintainer!
It already has a port, and a collection of hundreds of related ports, in an
entirely separate ports collection that the user must load into MacPorts in
order to use. The previous
On Mar 25, 2018, at 09:57, Joshua Root wrote:
> A port with no destroot phase will install no files. I doubt that is
> what you want.
Well it's technically possible to write a port that performs the destroot tasks
in an earlier phase. We'd prefer a port not do this, but some build systems are
On Mar 25, 2018, at 01:49, Jan Stary wrote:
> On Mar 24 14:14:37, Mojca wrote:
>> On 24 March 2018 at 13:54, Jan Starý wrote:
>>> The 'platforms' field of a Portfile is currently
>>> both _required_ and _ignored_. By the Guide,
>>>
>>>A list of the platforms on which the port has been
On Mar 24, 2018, at 08:14, Mojca Miklavec wrote:
>> I propose that the 'platforms' field be no longer required
>> if it is ignored, and if it stays, let it be a free form text,
>> as opposed to a predefined definitive list of all unixes.
>
> We'll need it to specify which darwin versions are
On Mar 24, 2018, at 04:49, Jan Stary wrote:
> what is the plan really with libressl and libressl-devel?
> We have 2.5.5 in security/libressl, 2.6.2 in security/libressl-devel,
> and now 2.7.1 is out.
>
> I would just prepare an udate of libressl to 2.7.1,
> but I want to as kfirst: why do we
On Mar 24, 2018, at 07:35, Andreas Falkenhahn wrote:
> When I compile my C++11 project on a 10.5 PPC system using gcc6 and try to
> run it on another 10.5 PPC system that doesn't have gcc6 installed, I get an
> error that a symbol cannot be imported from /usr/lib/libstdc++.6.dylib. I
> guess
On Mar 22, 2018, at 18:26, Qianqian Fang wrote:
> I don't know if this si common, but when I tried to install gdb (because my
> lazarus 1.8 complains about missing gdb) using
>
> sudo port install gdb
>
> I got an error when installing the dependency package xz, with the following
> error
>
On Mar 20, 2018, at 17:22, Jeremy Huddleston Sequoia wrote:
> On Mar 19, 2018, at 4:34 PM, Ryan Schmidt wrote:
>
>> Ok, I've figured out that the reason why I'm not seeing the "Unable to
>> determine location of a macOS SDK" message is that I was running MacPor
On Mar 19, 2018, at 11:21, db wrote:
> 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.
Hmm. I can't reproduc
On Mar 16, 2018, at 09:08, Marius Schamschula wrote:
> On Mar 16, 2018, at 9:05 AM, Ray Zimmerman wrote:
>
>> Octave 4.2.2 was released recently. Would love to have the octave port
>> updated, so I could benefit from the bug fixes.
>
> Waiting for maintainer: see:
On Mar 18, 2018, at 08:32, Andreas Falkenhahn wrote:
> There's just one little problem remaining: I cannot use gcc-ar-mp-6 because
> it reports the following error: "Cannot find plugin liblto_plugin.so".
> So I just use the "ar" that came with Xcode and it worked fine but maybe
> gcc-ar-mp-6
On Mar 19, 2018, at 08:03, Yanni wrote:
> I'm not sure if this has anything to do with macports but I am using macports
> to install a specific software called pymol. The laptop is 10.13.3 High
> Sierra and up to date.
>
> When I try to install it ("sudo port install pymol") I get the error:
On Mar 19, 2018, at 10:00, db wrote:
> 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
On Mar 16, 2018, at 03:11, Dave Horsfall wrote:
> What should I be using now?
Possibly git.
On Mar 15, 2018, at 07:18, pagani laurent via macports-users wrote:
> Hello,
>
> Running Mac OS 10.12.6, I try to install ATLAS with macports but 1) it
> selects /usr/bin/clang as a C compiler (why not the /opt/local/bin/gcc one ?),
MacPorts intentionally builds ports with specific compilers.
On Mar 10, 2018, at 18:15, Lenore Horner wrote:
> I don’t know whether the fetch errors are related at all.
Nope.
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 doesn't seem to exist in
> /opt/local/var/macports/incoming/verified
> Attempting to fetch
On Mar 10, 2018, at 18:51, Lenore Horner wrote:
> I just tried to run port upgrade outdated and a dependency of openscad
> (qscintilla-qt4) failed to upgrade. I still have the previous version of
> that dependency listed as active and only one version of port is listed as
> installed and it
On Mar 10, 2018, at 14:53, S. L. Garwood wrote:
> I need boost 1.65 … is it available on MacPorts? All I see is 1.66
No, MacPorts provides only the current version of a port.
Instructions for installing an older version of a port are here:
On Mar 10, 2018, at 14:24, db wrote:
> 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.
When you press tab, the bash completion code runs. Looking
On Mar 10, 2018, at 12:18, db wrote:
>
> 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
Are any MacPorts users or developers attending South by Southwest in Austin
(March 9-18)? Maybe we could meet up.
On Mar 7, 2018, at 19:28, Dave Horsfall wrote:
>> As always, changes are described in perldelta:
>>
>> http://search.cpan.org/dist/perl-5.26.0/pod/perldelta.pod#Removal_of_the_current_directory_(".")_from_@INC
>
> Aha - all is now clear! Was there actually a port note about it that I
>
tch. But since this one does offer a variable, you don't.
> On 2018-03-07, at 12:16, Ryan Schmidt wrote:
>
>> Presumably, you're meant to specify PREFIX=/opt/local in build.args.
>
> The advantage is not making a patch for Makefile.
Yes.
> combined:
> -
>
On Mar 6, 2018, at 09:01, pdv wrote:
> I'm trying to local install jdupes with my own test fixes, but i cannot
> destroot/activate due to more violation.
>
> how can i - without patching the Makefile, specify /opt/local as destination?
>
> logextract:
> ---
> # port install jdupes
>
On Mar 6, 2018, at 04:00, db wrote:
> 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 p
On Mar 6, 2018, at 03:47, db wrote:
> On 6 Mar 2018, at 02:34, Ryan Schmidt 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
On Mar 5, 2018, at 22:09, Ryan Schmidt wrote:
> On Mar 5, 2018, at 20:06, Dave Horsfall wrote:
>
>> A script that I wrote and has worked fine for ages is now breaking with:
>>
>> Can't locate Scanner.pm in @INC (you may need to install the Scanner
>> module)
On Mar 5, 2018, at 20:06, Dave Horsfall wrote:
> A script that I wrote and has worked fine for ages is now breaking with:
>
>Can't locate Scanner.pm in @INC (you may need to install the Scanner
> module) (@INC contains:
> /opt/local/lib/perl5/site_perl/5.26/darwin-thread-multi-2level
>
On Mar 5, 2018, at 05:43, db wrote:
> 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.
>
&g
On Mar 5, 2018, at 04:34, db wrote:
>
> I know, but I don't see how HEAD is pragmatically that much different from
> the devel ports that use a hash+date instead.
"HEAD" is not a specific version. It will vary as developers make new commits.
A user installing a port that fetches from "HEAD"
On Feb 28, 2018, at 01:12, Jan Stary wrote:
> Back to the original problem: using depends_fetch is not a solution
> to downloads of tar.gz failing on some https sites, right? Because
> whatever the port adds to depends_fetch, the https fetching will
> still be done with the (lib)curl macports
On Feb 26, 2018, at 00:57, Jan Stary wrote:
> On Feb 22 19:04:41, Jan Stary wrote:
>> On Feb 22 17:09:22, Rainer Mueller wrote:
>>> On 2018-02-21 20:14, Jan Stary wrote:
If I am reading https://guide.macports.org/chunked/reference.phases.html
right, there is are no "fetch
On Feb 26, 2018, at 13:40, Michael wrote:
> :info:configure Include the log file "ffbuild/config.log" produced by
> configure as this will help
> :info:configure solve the problem.
If you could show us this file, it might help.
The fix:
https://trac.macports.org/ticket/55878
On Feb 22 18:54:18, Jan Stary wrote:
> One of the libraries in MP providing SSL functionality is WolfSSL.
> Only two other ports mention it:
>
> sysutils/gearmand explicitly disables it
> net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
>
> Is anyone using it? Would there be any
On Feb 20, 2018, at 08:34, Joshua Kordani wrote:
> Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to make
> use of dylib's provided by macports in my own programs without setting this
> flag. I've read in several places that, esp with macports, this should not
> be
On Feb 19, 2018, at 13:37, Qianqian Fang wrote:
> I don't know what was changed recently, the built-in git command from Xcode
> stopped working with the following error
>
> fangq@jinwy:~/space/git/Project/autobuild/mcx$ git pull
> dyld: lazy symbol binding failed: Symbol not found: _iconv_open
On Feb 14, 2018, at 13:46, Ken Cunningham wrote:
> On 2018-02-14, at 5:56 AM, Ryan Schmidt wrote:
>
>
>> We will definitely never offer a user-facing feature for building the HEAD
>> version of a port's code.
>
>
> I completely recognize why you
On Feb 14, 2018, at 17:16, db wrote:
> 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?
>
On Feb 14, 2018, at 17:42, Michael wrote:
>> I think we should look at ways in which MacPorts is harder to use and see if
>> we can address those.
>
> I'd say that being able to install software without having to use sudo would
> be my number one.
Step 1: edit the sudoers file so that you
1101 - 1200 of 1456 matches
Mail list logo
