Re: [120643] trunk/dports/lang/eero-devel
Brandon,
In classic Bourne shell, $@ produces a single empty quoted string if there
are no shell parameters. ${1+$@} means expand $@ if and only if $1 is
set, even if it is set to an empty string. The Korn shell (specifically
ksh93, IIRC) introduced the interpretation of $@ that bash uses.
Thanks. I was not aware SH provided conditional substitutions. Even after 25
years of Unix, I’m still learning; that’s great!
As the Korn shell is open source now, it would not surprise me if that
replaced bash at some point, should Apple decide it needs a newer shell than
a GPL2-ed bash. zsh also has a permissive license (although some contributed
scripts are GPL; I haven't checked the version) and might also be an
alternative.
ZSH would be fine. I have dreadful memories of trying to use KSH. But, as far
as I am concerned, since I use SH-like shells only to write scripts, I would
not really care.
73s from F5RCS!
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
[120784] trunk/dports/devel/swig/Portfile
Revision: 120784
https://trac.macports.org/changeset/120784
Author: michaelld at macports.org
Date: 2014-06-06 19:48:24 -0700 (Fri, 06 Jun 2014)
Log Message:
---
swig-allegro: use allegro5, since it works.
Modified Paths:
--
trunk/dports/devel/swig/Portfile
Modified: trunk/dports/devel/swig/Portfile
===
--- trunk/dports/devel/swig/Portfile 2014-06-07 02:47:46 UTC (rev 120783)
+++ trunk/dports/devel/swig/Portfile 2014-06-07 02:48:24 UTC (rev 120784)
@@ -45,7 +45,7 @@
test.target check
array set bindings {
-allegro {port:allegro allegrocl}
+allegro {port:allegro5 allegrocl}
Are you sure that's the right allegro? The swig docs are saying that
allegrocl is Allegro Common Lisp:
http://www.swig.org/Doc3.0/Allegrocl.html#Allegrocl
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120643] trunk/dports/lang/eero-devel
On 6/6/14, Brandon Allbery allber...@gmail.com wrote:
On Fri, Jun 6, 2014 at 1:58 PM, Vincent vi...@macports.org wrote:
With the quotes. Pedantically ${1+$@} is most correct, but (a) I
suspect the case that protects against would fail anyway, and (b) on OS X
/bin/sh is bash which handles $@ as if it were ${1+$@}. (I do wonder
how long before Apple abandons bash though)
I must admit I fail to see what ${1+“$@”} exactly refers to…
In classic Bourne shell, $@ produces a single empty quoted string if
there are no shell parameters. ${1+$@} means expand $@ if and only if
$1 is set, even if it is set to an empty string. The Korn shell
(specifically ksh93, IIRC) introduced the interpretation of $@ that bash
uses.
As the Korn shell is open source now, it would not surprise me if that
replaced bash at some point, should Apple decide it needs a newer shell
than a GPL2-ed bash. zsh also has a permissive license (although some
contributed scripts are GPL; I haven't checked the version) and might also
be an alternative.
Wasn't zsh actually already the default shell in OS X previously back
in the early days of OS X, before Apple switched to bash? Or am I
mis-remembering and getting it mixed up with tcsh?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120643] trunk/dports/lang/eero-devel
From http://support.apple.com/kb/ta27005 The default shell (or command-line interface) used in Mac OS X 10.0 through 10.2.8 is tcsh (with 10.3 and 10.4 it's bash). With Mac OS X 10.2 or later, other interactive shells are included, such as bash and zsh. On Jun 7, 2014, at 12:15, Eric Gallager eg...@gwmail.gwu.edu wrote: Wasn't zsh actually already the default shell in OS X previously back in the early days of OS X, before Apple switched to bash? Or am I mis-remembering and getting it mixed up with tcsh? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120790] trunk/dports/science/missfits/Portfile
On Jun 7, 2014, at 10:24 AM, aron...@macports.org wrote: Revision 120790 Author aron...@macports.org Date 2014-06-07 09:24:58 -0700 (Sat, 07 Jun 2014) Log Message missfits: adopt abandoned port (addresses #43755) Modified Paths trunk/dports/science/missfits/Portfile Diff Modified: trunk/dports/science/missfits/Portfile (120789 = 120790) --- trunk/dports/science/missfits/Portfile2014-06-07 13:59:47 UTC (rev 120789) +++ trunk/dports/science/missfits/Portfile2014-06-07 16:24:58 UTC (rev 120790) @@ -8,7 +8,7 @@ categories science platforms darwin maintainerssaao.ac.za:tim -licenseGPL-3+ +licensegmail.com:Deil.Christoph aronnax open maintainer You added yourself as a license not a maintainer. :) descriptionMissFITS is a program that performs basic \ maintenance and packaging tasks on FITS files. ___ macports-changes mailing list macports-chan...@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-changes ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120643] trunk/dports/lang/eero-devel
On Sat, Jun 7, 2014 at 12:15 PM, Eric Gallager eg...@gwmail.gwu.edu wrote: On 6/6/14, Brandon Allbery allber...@gmail.com wrote: replaced bash at some point, should Apple decide it needs a newer shell than a GPL2-ed bash. zsh also has a permissive license (although some contributed scripts are GPL; I haven't checked the version) and might also be an alternative. Wasn't zsh actually already the default shell in OS X previously back in the early days of OS X, before Apple switched to bash? Or am I mis-remembering and getting it mixed up with tcsh? It was tcsh, following the FreeBSD standard userspace as Apple tends to do (indeed, fbsd still suggests tcsh as the default shell and uses it as root's shell). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120617] trunk/dports/devel
On Jun 3, 2014, at 11:50 AM, dev...@macports.org wrote:
Revision
120617
Author
dev...@macports.org
Date
2014-06-03 09:50:48 -0700 (Tue, 03 Jun 2014)
Log Message
appstream-glib: new port, provides objects and helper methods to help reading
and writing AppStream metadata.
Added Paths
• trunk/dports/devel/appstream-glib/
• trunk/dports/devel/appstream-glib/Portfile
• trunk/dports/devel/appstream-glib/files/
• trunk/dports/devel/appstream-glib/files/patch-configure.ac.diff
Diff
Added: trunk/dports/devel/appstream-glib/Portfile (0 = 120617)
--- trunk/dports/devel/appstream-glib/Portfile
(rev 0)
+++ trunk/dports/devel/appstream-glib/Portfile2014-06-03 16:50:48 UTC
(rev 120617)
@@ -0,0 +1,39 @@
+# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
+# $Id$
+
+PortSystem 1.0
+PortGroup github 1.0
+
+github.setuphughsie appstream-glib 0_1_6 appstream_glib_
Ports should use version numbers in dotted decimal format, e.g. 0.1.6,
especially if that is the format the project itself uses, which in
appstream-glib's case, it is:
$ appstream-util --version
Version:0.1.6
Where the projects use underscores or other version number component separators
in their github tag names, this should be fixed by manually setting the version
after the github.setup line, for example using strsed:
github.setuphughsie appstream-glib 0_1_6 appstream_glib_
version [strsed ${version} g/_/./]
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120790] trunk/dports/science/missfits/Portfile
On Jun 7, 2014, at 9:29 AM, Frank Schima m...@macports.org wrote: You added yourself as a license not a maintainer. :) Hi Frank, Good eye! Fixed in r120805. Thanks, Leo ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
