Get supported_archs from command line

I'd like to know a port's supported_archs from a command line script. "port info" doesn't appear to have a flag to display it. This Tcl script shows how to get the list of subports from a portfile: https://trac.macports.org/browser/contrib/mp-buildbot/tools/subports.tcl However it does this by

Re: Determine before installation whether a port can be installed

> On Jul 28, 2016, at 8:36 AM, m...@macports.org wrote: > > >> On Jul 27, 2016, at 6:19 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> Your suggestion seems like a variation of my "third possibility", which has >> the dis

Re: Determine before installation whether a port can be installed

On Jul 28, 2016, at 9:18 AM, Ken Cunningham wrote: > OK -- So - I am absolutely nobody at all on this list, so please take this > following idea gently. > > This work you're embarking on (specifying what systems a given port will > build on, and which it won't) would seem in fact to be very

Re: Determine before installation whether a port can be installed

On Jul 27, 2016, at 8:24 PM, Craig Treleaven wrote: > On Jul 27, 2016, at 12:09 AM, Ryan Schmidt wrote: > >> I would like MacPorts to be extended so that it can be determined in >> advance, from the command line, before running "port install", whether a >&

Re: Determine before installation whether a port can be installed

On Jul 28, 2016, at 2:06 AM, Artur Szostak wrote: > "... A better implementation would let the port indicate that a port builds > on macOS 10.X or older, or macOS 10.Y or newer. ..." > > This sounds like there is a need to allow encoding of version ranges. Right, *if* we make a MacPorts base

Re: Determine before installation whether a port can be installed

> On Jul 27, 2016, at 8:26 AM, m...@macports.org wrote: > > Hi Ryan, > > >> On Jul 26, 2016, at 10:09 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> I would like MacPorts to be extended so that it can be determined in >> advance, from t

Determine before installation whether a port can be installed

I would like MacPorts to be extended so that it can be determined in advance, from the command line, before running "port install", whether a port can be installed (barring unexpected build failures and bugs). Currently, MacPorts assumes any port can be installed on any system, which is not the

Re: Choice of compiler from compiler.whitelist

On Jul 22, 2016, at 1:16 AM, Mojca Miklavec wrote: > One more question: does >compiler.whitelist macports-gcc-6 macports-gcc-5 macports-gcc-4.9 ... > automatically add a runtime dependency on libgcc? It looks like it adds a library dependency on gcc6, which has a library dependency on

Re: Choice of compiler from compiler.whitelist

On Jul 21, 2016, at 12:15 PM, Mojca Miklavec wrote: > What's the best way to blacklist all clang compilers and any old gcc? > (It's about a temporary bug mentioned in the other topic.) > > > Here's my attempt: > > PortGroup compiler_blacklist_versions 1.0 > > # blacklist any clang

Re: Build Systems

On Jul 19, 2016, at 11:33 AM, Daniel J. Luke wrote: > On Jul 19, 2016, at 12:09 PM, Ryan Schmidt wrote: >>>> Considering all the various build systems we encounter in MacPorts, from >>>> autotools to xcodebuild to cmake to scons to qmake to manually crafted &g

Re: Software that doesn't use DESTROOT and funny tarball directories

On Jul 19, 2016, at 10:49 AM, Watson Ladd wrote: > We've got it building, the problems outstanding are one easy upstream patch > and its tendency to fetch things during build/vendored zlib. > > Personally I'm not volunteering to maintain distribution patches to fix the > fetch and zlib issues.

Re: Software that doesn't use DESTROOT and funny tarball directories

On Jul 19, 2016, at 10:49 AM, Daniel J. Luke wrote: > On Jul 19, 2016, at 11:44 AM, Ryan Schmidt wrote: >> Without reading those links, I already know autotools sucks, and from the >> standpoint of a software developer I don't really enjoy writing autotools >>

Re: portfile test for macosx 10.6.8 + libc++

On Jul 19, 2016, at 9:52 AM, Ken Cunningham wrote: > You are completely correct, of course - upstream fixes would be ideal, and > much preferred over fixing the portfile to repair upstream deficiencies. Most > ports that use configure already seem to get these things brought in from the >

Re: Software that doesn't use DESTROOT and funny tarball directories

On Jul 19, 2016, at 10:37 AM, Daniel J. Luke wrote: > On Jul 19, 2016, at 8:19 AM, Ryan Schmidt wrote: >> This is one of the problems with projects that roll their own nonstandard >> configure scripts and Makefiles -- they don't work the way anybody >> unfamiliar with

Reason why default rsync URL was changed to a tarball

sources.conf used to default to: rsync://rsync.macports.org/release/ports/ [default] Since r79599 it defaults to: rsync://rsync.macports.org/release/tarballs/ports.tar [default] though not all of our documentation was updated to match. The commit message says "make sync and selfupdate via

Re: [150102] trunk/dports/perl/p5-gearman-server/Portfile

On Jul 19, 2016, at 10:01 AM, David Evans wrote: > On 7/19/16 5:41 AM, Ryan Schmidt wrote: >> >>> On Jul 12, 2016, at 7:16 AM, dev...@macports.org wrote: >>> >>> Revision >>> 150102 >>> Author >>> dev...@macports.org >>&g

Re: portfile test for macosx 10.6.8 + libc++

On Jul 19, 2016, at 8:25 AM, Ken Cunningham wrote: > Perfect. Thanks! > > There are a series of EFI32 machines stuck at 10.6.8 or at most 10.7. These > can be EFI-hacked to run 10.11 but that hasn't worked for me yet. > > I have found that almost any port I have tried to install can be

Re: [150062] trunk/dports/devel/npm3/Portfile

> On Jul 10, 2016, at 5:03 PM, ciserl...@macports.org wrote: > > Revision > 150062 > Author > ciserl...@macports.org > Date > 2016-07-10 15:03:52 -0700 (Sun, 10 Jul 2016) > Log Message > > npm3: update to version 3.10.5 > Modified Paths > > • trunk/dports/devel/npm3/Portfile > Diff > >

Re: [150102] trunk/dports/perl/p5-gearman-server/Portfile

> On Jul 12, 2016, at 7:16 AM, dev...@macports.org wrote: > > Revision > 150102 > Author > dev...@macports.org > Date > 2016-07-12 05:16:16 -0700 (Tue, 12 Jul 2016) > Log Message > > p5-gearman-server: update to version 1.130.1, homepage, dependencies. > Modified Paths > > •

Re: Software that doesn't use DESTROOT and funny tarball directories

On Jul 19, 2016, at 7:13 AM, Ryan Schmidt wrote: > On Jul 17, 2016, at 12:31 AM, Watson Ladd wrote: > >> The problem is that >> they want you to run configure with an argument indicating the install >> prefix, then don't seem to support DESTROOT. I've gone to upstream

Re: Software that doesn't use DESTROOT and funny tarball directories

On Jul 17, 2016, at 12:31 AM, Watson Ladd wrote: > I'm trying to write a portfile for ChezScheme. Thanks! > The problem is that > they want you to run configure with an argument indicating the install > prefix, then don't seem to support DESTROOT. I've gone to upstream to > report this, but I

Re: Always indicating license versions (was: Re: [150207] trunk/dports/perl/p5-net-cidr-lite/Portfile)

On Jul 15, 2016, at 3:21 PM, Daniel J. Luke wrote: > On Jul 14, 2016, at 11:13 PM, Ryan Schmidt wrote: >>> I'm asking what the utility is of having a middle ground between "we know >>> what this license is" and "we don't know what this license is" >&

Re: [150207] trunk/dports/perl/p5-net-cidr-lite/Portfile

On Jul 14, 2016, at 10:17 AM, Daniel J. Luke wrote: > On Jul 14, 2016, at 11:14 AM, Brandon Allbery wrote: >> On Thu, Jul 14, 2016 at 11:07 AM, Daniel J. Luke wrote: >>> I don't think it's useful to define a status for "it's unclear which >>> version of a license this falls under". (what kind of

Re: [150207] trunk/dports/perl/p5-net-cidr-lite/Portfile

On Jul 13, 2016, at 8:43 AM, Daniel J. Luke wrote: > On Jul 13, 2016, at 9:36 AM, m...@macports.org wrote: >> Or does simply stating “GPL” cover that already and that is why it has >> always been that way? > > 'GPL' by itself means 'any version of the GPL' > > From

Re: [149372] trunk/dports/x11/xglobe/files

> On Jun 15, 2016, at 2:51 PM, dl...@macports.org wrote: > > Revision > 149372 > Author > dl...@macports.org > Date > 2016-06-15 12:51:38 -0700 (Wed, 15 Jun 2016) > Log Message > > xglobe: update my marker location > Modified Paths > > •

Re: port ide command?

On Jul 4, 2016, at 4:05 AM, René J.V. Bertin wrote: > Would it make sense to consider something like a `port ide > [ide-options]` command which starts an IDE of choice with the environment set > appropriately for MacPorts? Or are there too few port developers who would > use such a feature

Re: [MacPorts] #51664: Please add pseudo-portnames for some common programs

On Jul 1, 2016, at 8:17 AM, Rainer Müller wrote: > Anyway, in order to let 'port install' suggest candidates or > alternatives based on binary names, we first need a database of port > contents. > > This use case would be an example what such an index could be used for. > I would also say that

Re: [MacPorts] #51726: Gildas Install Fail

On Jun 30, 2016, at 4:54 AM, Sébastien Maret wrote: > > I don't think that "sudo gcc select" has an effect on the compiler which is > used to build this port. There is a patch that forces the use of a specific > version of the compiler (clang for C and C++ and

Re: [MacPorts] #51664: Please add pseudo-portnames for some common programs

On Jun 30, 2016, at 7:25 AM, Rainer Müller wrote: > > Even with that, the proposal would not work for everything. There is no > port that provides a 'python' binary. The GNU coreutils are provided > with a 'g' prefix, in order not to override standard system utils by > default. Searching for the

Re: Captcha error when logging ticket

On Jun 22, 2016, at 8:54 AM, Rainer Müller wrote: > On 2016-06-22 06:42, Ryan Schmidt wrote: >> On Jun 21, 2016, at 2:15 PM, Chris Gorman wrote: >> >>> I am trying to log a bug today but cannot due to a captcha error. Any >>> ideas about what might be wrong?

Re: Captcha error when logging ticket

On Jun 21, 2016, at 2:15 PM, Chris Gorman wrote: > I am trying to log a bug today but cannot due to a captcha error. Any ideas > about what might be wrong? Your ticket might contain a word flagged as spam. You can check the BadContent wiki page for the list of spam words.

Re: Search in packages contents

On Jun 20, 2016, at 7:30 AM, Michele Venturi wrote: > As I've discussed with raim on irc I would like to be able to search the > packages' contents for a certain file. This could be done via the web or the > cli once a buildbot has compiled the list maybe in the form of a sqllite > database

Re: snapd

On Jun 18, 2016, at 1:00 AM, Mojca Miklavec wrote: > I would absolutely *love* > to be able to install MacPorts (or HomeBrew or snap or anything else > for that matter) and create a port/package where I would list the > dependencies and then make a package that would automatically generate > a

Re: [149404] trunk/dports/devel/zmq/Portfile

> On Jun 17, 2016, at 3:49 PM, strom...@macports.org wrote: > > Revision > 149404 > Author > strom...@macports.org > Date > 2016-06-17 13:49:27 -0700 (Fri, 17 Jun 2016) > Log Message > > zmq: update to version 4.1.5 > Modified Paths > > • trunk/dports/devel/zmq/Portfile > homepage

Re: snapd

On Jun 17, 2016, at 12:34 PM, Alexey Kuznetsov wrote: > > On Fri, Jun 17, 2016 at 8:26 PM, Ryan Schmidt wrote: >> Again: why? What problem are you trying to solve? > > I think snapd is a good point to try to start to be together. May be because > no one tried three separat

Re: snapd

On Jun 17, 2016, at 11:58 AM, Alexey Kuznetsov wrote: > > On Fri, Jun 17, 2016 at 7:42 PM, Brandon Allbery wrote: > >> You're missing the point that those distributions are all based on Linux, >> and Portfiles exist because OS X is not Linux and many packages need to be >> beat over the head

Re: snapd

On Jun 17, 2016, at 11:38 AM, Alexey Kuznetsov wrote: > On Fri, Jun 17, 2016 at 7:32 PM, Ryan Schmidt wrote: > >> On Jun 17, 2016, at 11:24 AM, Alexey Kuznetsov wrote: >> >> > Universal “snap” packages launch on multiple Linux distros >> > >> > htt

Re: snapd

On Jun 17, 2016, at 11:24 AM, Alexey Kuznetsov wrote: > Universal “snap” packages launch on multiple Linux distros > > https://insights.ubuntu.com/2016/06/14/universal-snap-packages-launch-on-multiple-linux-distros/ > > Even OpenWRT on the list. Why not join? Do I understand correctly that

Re: xcodebuild SKIP_INSTALL

On Jun 13, 2016, at 3:35 AM, Alexey Kuznetsov wrote: > On Mon, Jun 13, 2016 at 7:50 AM, Ryan Schmidt wrote: > >> On Jun 12, 2016, at 9:34 AM, Alexey Kuznetsov wrote: >>> >>> I'm updating MenuMeters port file to the latest OS X El Capitan os version. >>&g

Re: xcodebuild SKIP_INSTALL

On Jun 12, 2016, at 9:34 AM, Alexey Kuznetsov wrote: > > I'm updating MenuMeters port file to the latest OS X El Capitan os version. > And it face few issues. I solve them, but not sure if it is best practice. > > First) of all 'xcode.destroot.settings SKIP_INSTALL=YES' seems ignored by >

Re: [149320] trunk/dports/lang/qore-mysql-module

On Jun 11, 2016, at 11:07 AM, Bradley Giesbrecht wrote: > Base should be enhanced to allow dots “.” in variant names. > > We could then write variant names like "mariadb10.0” and “mariadb10.1" > instead of the ambiguous “mariadb100” and “mariadb101”. Yup. As I recall there was some

Re: permissions of DESTROOT

On Jun 11, 2016, at 10:51 AM, JASON TILLEY wrote: > I am attempting to create my first port in a local repository. I can get it > to configure, but it seems to be having trouble installing into destroot. I > get the error: > > for i in libnn.a; do \ > /usr/bin/install -c -m 644 $i

Re: [149319] trunk/dports/lang/qore-yaml-module/Portfile

> On Jun 11, 2016, at 1:01 AM, davidnich...@macports.org wrote: > > Revision > 149319 > Author > davidnich...@macports.org > Date > 2016-06-10 23:01:57 -0700 (Fri, 10 Jun 2016) > Log Message > > qore-yaml-module: updated to v0.5 > Modified Paths > > •

Re: [149312] trunk/dports/python/py-ngl/Portfile

> On Jun 10, 2016, at 3:51 PM, dstru...@macports.org wrote: > > Revision > 149312 > Author > dstru...@macports.org > Date > 2016-06-10 13:51:48 -0700 (Fri, 10 Jun 2016) > Log Message > > py-ngl: Add test phase. > Modified Paths > > • trunk/dports/python/py-ngl/Portfile > Diff > >

Re: [149308] trunk/dports/science/paraview/Portfile

> On Jun 10, 2016, at 12:31 PM, dstru...@macports.org wrote: > > Revision > 149308 > Author > dstru...@macports.org > Date > 2016-06-10 10:31:56 -0700 (Fri, 10 Jun 2016) > Log Message > > paraview: Previous commit (because of +testing) should have increased > revision. > ---

Re: Weird situation after updating paho-mqtt

On Jun 10, 2016, at 05:17, Rainer Müller wrote: > > As far as I know, the distfiles are only fetched with a daily cronjob, > that may take a while. Currently, the script only runs twice a week: https://trac.macports.org/ticket/50875 ___ macports-dev

Re: [149146] trunk/dports/math

> On Jun 1, 2016, at 6:41 PM, mcalh...@macports.org wrote: > > Revision > 149146 > Author > mcalh...@macports.org > Date > 2016-06-01 16:41:20 -0700 (Wed, 01 Jun 2016) > Log Message > > octave family: writing to a plist file with /usr/bin/defaults is deprecated; > use PlistBuddy instead

Re: [149178] trunk/dports/audio/pulseaudio/Portfile

> On Jun 4, 2016, at 4:56 PM, io...@macports.org wrote: > > Revision > 149178 > Author > io...@macports.org > Date > 2016-06-04 14:56:53 -0700 (Sat, 04 Jun 2016) > Log Message > > pulseaudio: add esound variant. Revbump. > Modified Paths > • trunk/dports/audio/pulseaudio/Portfile > Diff >

Re: [MacPorts] #51547: xorg-xcb-proto fails to install, bad python version check

Generally, you should respond to a ticket by visiting the ticket URL in your web browser and writing in the form. In this case: >> Ticket URL: ___ macports-dev mailing list

Re: [MacPorts] #51547: xorg-xcb-proto fails to install, bad python version check

On Jun 3, 2016, at 05:07, artist.impressionist@... wrote: > >> On 6/3/16, 00:07, "MacPorts" wrote: >> >> Comment (by jeremyhu@…): >> >> Please provide your config.log as indicated by the terminal output when >> you encounter the error. >> >> -- >> Ticket URL:

Re: Portfile for binary only install

On May 27, 2016, at 4:31 PM, Sean wrote: > Looking to create a portfile for a package that only distributes pre-compiled > binaries. > > In this case, package.tbz expands to: > > package > └─ bin/ > └─ share/ > └─ lib/ > > Is the most idiomatic way to eliminate the config, build, and test

Re: Howto inspect Portfile variables to debug install

On May 30, 2016, at 6:33 AM, Mojca Miklavec wrote: > On 29 May 2016 at 20:19, Chris Gorman wrote: >> Hello, >> >> I was wondering how to inspect variables in a port file. Specifically, I >> want to apply a patch conditionally if perl is version 5.10.0. >> >> I'm trying something like >> >>

Re: platform{} statement

On May 29, 2016, at 05:07, René J.V. Bertin wrote: > > The documentation states that the platform{} syntax for specifying platform > variants doesn't allow you to specify a range of platforms. That still seems > to be accurate. Correct, except that the term "platform

Re: Going on holiday

On May 23, 2016, at 3:17 PM, David Evans wrote: > Later this week, I will be heading out of the country on holiday for about a > month in exotic locations where the > internet may only be a rumor. Not taking a computer either. Should be back > toward the end of June

Re: Debian/Ubuntu-style -dev ports

On May 19, 2016, at 5:50 AM, René J.V. Bertin wrote: > One could, the real question is, should we? I think a main MacPorts guideline > has always been to keep dependencies as simple as possible by not splitting > up ports even if they can. Qt has always allowed (and advised) building each >

Re: Mac Port Git issues breaking multiple ports

On May 13, 2016, at 4:58 AM, John Patrick wrote: > Any update on the git ssl certificate issues when trying to close > repositories? > > I'm aware it affects ports for git-flow and ansible. > > https://trac.macports.org/ticket/49539 > https://trac.macports.org/ticket/50467 >

Re: [148665] trunk/dports/net/aria2/Portfile

> On May 13, 2016, at 7:16 PM, io...@macports.org wrote: > > Revision > 148665 > Author > io...@macports.org > Date > 2016-05-13 17:16:17 -0700 (Fri, 13 May 2016) > Log Message > > aria2: fix builds in trace mode and potentially also normal mode. > > use_autoreconf must either be set after

Re: [148683] trunk/dports/devel/apache-ant/Portfile

> On May 14, 2016, at 9:16 PM, bl...@macports.org wrote: > > Revision > 148683 > Author > bl...@macports.org > Date > 2016-05-14 19:16:09 -0700 (Sat, 14 May 2016) > Log Message > > apache-ant: build +source variant build failure. > > bash-3.2# /opt/local/bin/port -v build apache-ant +source >

Re: os.major etc. on Linux

On May 13, 2016, at 5:52 AM, René J.V. Bertin wrote: > On Friday May 13 2016 05:00:21 Ryan Schmidt wrote: > >> I'm not giving that any thought. MacPorts is about installing software on OS >> X. > > You mean it really should be renamed to OSXPorts? ^^ The &qu

Re: os.major etc. on Linux

> On May 13, 2016, at 4:49 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Friday May 13 2016 04:23:24 Ryan Schmidt wrote: > >> I think we've established that os_arch should only be i386 or powerpc. > > Side-ways related: do we have an idea (or can we hav

Re: os.major etc. on Linux

On May 13, 2016, at 4:18 AM, René J.V. Bertin wrote: > On Friday May 13 2016 03:54:26 Ryan Schmidt wrote: > >>> If build_arch is not set then os.arch is used as a fallback. No doubt we >>> don't detect an appropriate default for build_arch on Linux. >> >&

Re: os.major etc. on Linux

On May 13, 2016, at 3:48 AM, Joshua Root wrote: > On 2016-5-13 18:13 , Ryan Schmidt wrote: >> >> On May 13, 2016, at 3:07 AM, René J.V. Bertin wrote: >> >>> On Friday May 13 2016 15:21:53 Joshua Root wrote: >>> >>>>>> Side-ways rela

Re: os.major etc. on Linux

On May 13, 2016, at 3:45 AM, René J.V. Bertin wrote: > On Friday May 13 2016 03:13:19 Ryan Schmidt wrote: > >> os_arch is the way ports and probably MacPorts base differentiates an Intel >> computer from a PowerPC computer. It is not a mechanism to determine the >&

Re: *-devel ports for llvm and gcc

> On May 12, 2016, at 3:51 AM, René J. V. Bertin <rjvber...@gmail.com> wrote: > > Ryan Schmidt wrote: > > >>> is released as a stable version it should be renamed to llvm-3.9. The >>> ports llvm-3.9 and llvm-3.9-devel are still drop-in replacements. &

Re: os.major etc. on Linux

On May 13, 2016, at 3:07 AM, René J.V. Bertin wrote: > On Friday May 13 2016 15:21:53 Joshua Root wrote: > Side-ways related: why is os_arch reset to i386 from x86_64 on line 636? >From what I've seen that causes packages to be labelled and registered as i386 (i.e. 32bit) when

Re: os.major etc. on Linux

On May 12, 2016, at 5:37 AM, René J.V. Bertin wrote: > On Thursday May 12 2016 11:57:21 Rainer Müller wrote: > >> I would consider this a bug. > > Me too, if we're sure it isn't a feature ;) > >> We take this directly from >> $tcl_platform(osVersion), which is equivalent to `uname -r`. >> >>

Re: file/dir name case (in)sensitivity

On May 6, 2016, at 12:51 PM, René J.V. Bertin wrote: > On Friday May 06 2016 17:42:14 Clemens Lang wrote: > > Hi, > >> Our buildbots use case-sensitive filesystems, so you should be able to >> use binary packages for both case-insensitive machines (the >> configuration most people are probably

Re: [148369] trunk/dports/math/qhull

> On May 5, 2016, at 12:33 PM, vi...@macports.org wrote: > > Revision > 148369 > Author > vi...@macports.org > Date > 2016-05-05 10:33:15 -0700 (Thu, 05 May 2016) > Log Message > > qhull: bump to 7.2 (a.k.a. 2015.2) > Modified Paths > > • trunk/dports/math/qhull/Portfile > Removed Paths

Re: *-devel ports for llvm and gcc

On May 4, 2016, at 10:35 AM, Bradley Giesbrecht <pixi...@macports.org> wrote: > > On May 4, 2016, at 7:47 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> On May 4, 2016, at 9:38 AM, Rainer Müller <rai...@macports.org> wrote: >> >>> U

Re: *-devel ports for llvm and gcc

> On May 4, 2016, at 9:38 AM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-05-04 15:20, Ryan Schmidt wrote: >>> In my opinion, llvm-3.8 and llvm-3.9 should really have a -devel >>> prefix as long as they provide pre-releases. The same also applies >

Re: automatic choice of a default +llvmXY variant via selected compiler?

On Apr 29, 2016, at 3:20 AM, René J.V. Bertin wrote: > On Thursday April 28 2016 21:37:53 Ryan Schmidt wrote: > >>> I would think that an adaptive mechanism to determine a default variant >>> isn't incompatible with reproducible builds (or at least an accepted/able

Re: *-devel ports for llvm and gcc (was: Re: automatic choice of a default +llvmXY variant via selected compiler?)

> On Apr 29, 2016, at 9:19 AM, Rainer Müller <rai...@macports.org> wrote: > > On 2016-04-29 04:37, Ryan Schmidt wrote: >> When multiple version variants are available, we usually suggest you >> default to the latest stable version. Right now that's llv

Re: failed to uninstall part of files. CIVL

On May 3, 2016, at 7:10 PM, Abdulrahman Alshammari wrote: > Hey, > The attached portfile is working now perfectrly after fixing some issue. I am > not sure if what I did is the right one or there is something better than > this. When I install civl, it works fine, but when I uninstall it, the

Re: buildbots with old ssl (snowleopard, mtln)

> On May 4, 2016, at 7:50 AM, Daniel J. Luke <dl...@geeklair.net> wrote: > > On May 4, 2016, at 8:48 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >>> If we can force a mirror of openssl in the meantime (if it's not there >>> already), it would be us

Re: buildbots with old ssl (snowleopard, mtln)

On May 4, 2016, at 7:47 AM, Daniel J. Luke <dl...@geeklair.net> wrote: > On May 4, 2016, at 8:46 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >> On May 4, 2016, at 1:58 AM, Joshua Root wrote: >>> Probably the best fix on our end would be to reinstate the imme

Re: buildbots with old ssl (snowleopard, mtln)

On May 4, 2016, at 1:58 AM, Joshua Root wrote: > Probably the best fix on our end would be to reinstate the immediate > mirroring that used to happen from a post-commit hook. And possibly make the > build block until the mirroring is done. In fact, maybe the mirroring could > be triggered

Re: [148264] trunk/dports/net/snort/Portfile

> On May 1, 2016, at 6:55 PM, m...@macports.org wrote: > > Revision > 148264 > Author > m...@macports.org > Date > 2016-05-01 16:55:29 -0700 (Sun, 01 May 2016) > Log Message > > snort 2.9.8.2: add openssl dependency (missing headers) for El Cap > Modified Paths > > •

Re: [148268] trunk/dports/sysutils

> On May 1, 2016, at 7:51 PM, m...@macports.org wrote: > > Revision > 148268 > Author > m...@macports.org > Date > 2016-05-01 17:51:21 -0700 (Sun, 01 May 2016) > Log Message > > rkhunter: new port (#16792) > Some comments: > --- trunk/dports/sysutils/rkhunter/Portfile

Re: [148279] trunk/dports/math/dolfin/Portfile

> On May 2, 2016, at 6:22 PM, m...@macports.org wrote: > > Revision > 148279 > Author > m...@macports.org > Date > 2016-05-02 16:22:07 -0700 (Mon, 02 May 2016) > Log Message > > dolfin: add vtk6 variant to enable El Capitan builds (#50815, maintainer > timeout). > +variant vtk6 description

Re: civl and z3 _ error when I install them locally.

On Apr 28, 2016, at 9:23 PM, Ryan Schmidt wrote: > You can override the destroot phase with: > > destroot { >system -C ${worksrcpath} "java -jar filename.jar" > } Sorry, I've made the same mistake twice: it's

Re: Github Checksums ..

On Apr 16, 2016, at 9:55 AM, Rainer Müller wrote: > On 2016-04-16 02:54, Brandon Allbery wrote: >> Yes, that's what I meant. You want to point to archives, because they >> don't change; tarballs will be regenerated on the fly by github, so they >> do not have fixed checksums and you would have

Re: automatic choice of a default +llvmXY variant via selected compiler?

On Apr 9, 2016, at 3:29 AM, René J.V. Bertin wrote: > The KF5 version of the KDevelop IDE uses libclang for its C/C++ parser, and > requires a clang installation that includes llvm-config. Apple doesn't > include that utility (and possibly other required components) in its > toolchain, so one

Re: civl and z3 _ error when I install them locally.

On Apr 28, 2016, at 9:03 PM, Abdulrahman Alshammari wrote: > On Apr 28, 2016, at 9:29 PM, Ryan Schmidt wrote: > >> On Apr 28, 2016, at 8:08 PM, Abdulrahman Alshammari wrote: >> >>> Hey, >>> I am working in parallel between two ports. some of the tickets a

Re: civl and z3 _ error when I install them locally.

On Apr 28, 2016, at 8:08 PM, Abdulrahman Alshammari wrote: > Hey, > I am working in parallel between two ports. some of the tickets are useful > and get results. Some of them I get lost when I read them. > > For civl: I got this error > :error:destroot org.macports.destroot for port civl

Re: ports that contain JAR file

On Apr 22, 2016, at 9:43 PM, Abdulrahman Alshammari wrote: > On Apr 22, 2016, at 10:36 PM, Ryan Schmidt wrote: > >> On Apr 22, 2016, at 3:46 PM, Abdulrahman Alshammari wrote: >> >>> The original installation of the software that I am trying to make a port >>

Re: ports that contain JAR file

On Apr 22, 2016, at 3:46 PM, Abdulrahman Alshammari wrote: > The original installation of the software that I am trying to make a port > for, is using the command line: > Java -jar filename.jar > > Is there a port of software that used to use the same way of installation > before the port

Re: Fail port when using Local repository

On Apr 20, 2016, at 11:22 PM, Abdulrahman Alshammari wrote: > > I want to check if the local port works fine with the portfile I added > locally. I follow the instruction in the documentation. I got this error: > > Failed to parse file devel/civl/Portfile: invalid command name "(2)" The

date in verbose port installed output: should it include time zone?

r146757 added date information to the output of `port -v installed`, e.g.: $ port -v installed zlib The following ports are currently installed: zlib @1.2.8_1+universal (active) platform='darwin 15' archs='i386 x86_64' date='2016-04-12 13:52:04' I'm concerned that this is not displaying a

Re: Errors should probably come after notes?

> On Apr 8, 2016, at 4:23 PM, Mojca Miklavec wrote: > >> That's a tough question -- you wouldn't want users to miss the notes, >> either. > > Sure. But notes can get pages long and when doing a mere upgrade they > are often irrelevant ("if you want to make this version of X

Re: [MacPorts] #51077: openmpi-devel: openmpi-dev-3727-g7523357.tar.bz2 does not exist (was: openmpi-dev-3727-g7523357 doesn't exist)

On Apr 6, 2016, at 8:46 PM, G A wrote: > Thanks for the help. Please write your reply in the ticket, by visiting the ticket URL in your web browser and writing in the form, so that the conversation stays in one place: >> Ticket URL:

Re: variants

On Apr 3, 2016, at 2:40 AM, Takeshi Enomoto wrote: > It seems that variants in default_variants are not proliferated as > those specified in the command-line. > I have this problem with some ports that I maintain and > cause build failures with the buildbots. > > I would be helpful if you help

Re: openbrowser

On Apr 2, 2016, at 2:16 PM, Mark Brethen wrote: > > Ryan, > > I received an error message from openbrowser: > > starting help: openbrowser /opt/local/share/doc/CalculiX/cgx_2.10/cgx/cgx.html > parse_plist_file: file >

Re: html and postscript viewer

> On Apr 1, 2016, at 23:03, Mark Brethen wrote: > > I’ve run into a snag building calculix. glut and libSNL are libraries that > calculix uses. I set > > "compiler.whitelist macports-gcc-4.9” > > per the developers instructions. Why? We usually do not want to

Re: html and postscript viewer

On Apr 1, 2016, at 19:03, Mark Brethen wrote: > > Would someone look at the patch file and comment if okay or needs changes. You should remove -L/usr/X11R6/lib; we don't want to get any libraries from there. We want to use the versions installed in ${prefix} by

Re: multiple distfiles from multiple sources and with multiple compression types

On Mar 31, 2016, at 11:35 AM, Rainer Müller wrote: > Using magic bytes would even result in wrong results in some cases. For > example for scapy, the distfile is intentionally a polyglot. It is both > a valid shell script and a zip file: > > $ file -b

Re: [147186] trunk/dports/net/nmap/Portfile

> On Mar 31, 2016, at 1:50 PM, Daniel J. Luke wrote: > > On Mar 31, 2016, at 2:45 PM, Daniel J. Luke wrote: >> Does default_variants not work like other commands? I would have expected >> default_variants-append here (and/or would rather be able to do

Re: html and postscript viewer

On Mar 30, 2016, at 21:17, Mark Brethen wrote: > > I suppose these launch scripts will need to be installed in ${prefix}/bin. No need for custom scripts. Set PSVIEWER to "open" (part of OS X) and BROWSER to "openbrowser" (and add a dependency on my openbrowser port).

Re: html and postscript viewer

> On Mar 30, 2016, at 8:36 PM, Kevin Walzer <k...@codebykevin.com> wrote: > > On 3/30/16 9:28 PM, Ryan Schmidt wrote: >> /usr/bin/open is not necessarily suitable. For example, I have configure my >> system so that if I `open` a .html file, it opens into my text edito

Re: html and postscript viewer

On Mar 30, 2016, at 8:21 PM, Kevin Walzer wrote: > On 3/30/16 9:11 PM, Mark Brethen wrote: >> Culculix CGX is setting a default html (firefox) and postscript (gv) viewer. >> For mac users, they recommend changing ‘gv’ to ‘preview’ but give no >> recommendation for a browser. I thought I’d ask

Re: multiple distfiles from multiple sources and with multiple compression types

On Mar 30, 2016, at 3:06 PM, Mojca Miklavec wrote: > On 30 March 2016 at 19:25, René J. V. wrote: >> >>> It is fairly obvious how to extract these files. There is usually no >>> need to specify how these files should be extracted, since most >>> compression methods can be deduced from the

<    1   2   3   4   5   6   7   8   9   10   >