Update devel/py-robotframework from version 2.8.2 to 2.8.3. This a bug fixing update, mostly about java.
An important note. With stage allowed, at least one file (islike.py) is not installed. I'm not sure if this deserves a separate PR...
Fix: Patch attached with submission follows:
freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool)
Sorry, I forget to update plist. Corrected patch attached.
I'll take it.
Committed, with minor changes. Thanks!
Date: Fri Dec 6 12:32:18 2013
New Revision: 335741
devel/py-robotframework: update to 2.8.3
Submitted by: maintainer
--- head/devel/py-robotframework/Makefile Fri Dec 6 12:25:48 2013 (r335740)
+++ head/devel/py-robotframework/Makefile Fri Dec 6 12:32:18 2013 (r335741)
@@ -2,7 +2,7 @@
CATEGORIES= devel www python
@@ -14,5 +14,6 @@ LICENSE= AL2
--- head/devel/py-robotframework/distinfo Fri Dec 6 12:25:48 2013 (r335740)
+++ head/devel/py-robotframework/distinfo Fri Dec 6 12:32:18 2013 (r335741)
@@ -1,2 +1,2 @@
-SHA256 (robotframework-2.8.2.tar.gz) = da1cb3318a349a7c359a4f0c78d75c87561791f12235dc48551400bee2bf6c5f
-SIZE (robotframework-2.8.2.tar.gz) = 568721
+SHA256 (robotframework-2.8.3.tar.gz) = bb8ca9bad5152a3ac19e4dfc6e097324b31a4a8879d66c268e61d3eb577fd2f4
+SIZE (robotframework-2.8.3.tar.gz) = 570523
email@example.com mailing list
To unsubscribe, send any mail to "firstname.lastname@example.org"
wg@, thanks for committing.
Frankly speaking, I do not think a change from static pkg-plist to a dynamic one
is a minor change... The port works fine with a corrected static plist and no
NO_STAGE line, I have checked that.
Do I understand correctly, that a port without NO_STAGE=yes uses pkg-plist for
installing from the stage dir to the destination dir? If so, then dynamic plist
can be used to find the list of installed files for pkg-plist generation, but is
not needed in normal use.
Previously, I used 'port test' (from ports-mgmt/porttools) to find changes in
plist. Probably, porttools can be fixed for this task also with staging. Else,
a maintainer (me in case of devel/py-robotframework) can use dynamic plist for
generating the static one. I still believe a static plist is better, as the
It would be nice to have something about staging in porters-handbook, actually.
Now I'm guessing what staging is doing and what it needs...
My version of porters-handbook was too old. The new one has all the needed information on staging IMHO.