Re: [124592] trunk/dports/devel/ocaml-ctypes/Portfile
On Aug 26, 2014, at 3:21 AM, m...@macports.org wrote:
Revision
124592
Author
m...@macports.org
Date
2014-08-26 01:21:23 -0700 (Tue, 26 Aug 2014)
Log Message
ocaml-ctypes: version 0.3
Modified Paths
• trunk/dports/devel/ocaml-ctypes/Portfile
Diff
Modified: trunk/dports/devel/ocaml-ctypes/Portfile (124591 = 124592)
--- trunk/dports/devel/ocaml-ctypes/Portfile 2014-08-26 08:15:27 UTC (rev
124591)
+++ trunk/dports/devel/ocaml-ctypes/Portfile 2014-08-26 08:21:23 UTC (rev
124592)
@@ -4,7 +4,7 @@
PortGroup ocaml 1.0
nameocaml-ctypes
-version 0.2.2
+version 0.3
categories devel ml
platforms darwin
license BSD
@@ -12,17 +12,18 @@
description Library for binding to C libraries using pure OCaml
long_description${description}
homepagehttps://github.com/ocamllabs/ocaml-ctypes
-master_sites
https://codeload.github.com/ocamllabs/ocaml-ctypes/tar.gz/
-distfiles ocaml-ctypes-${version}
-checksums rmd160 97b380a84d1043ff4c1fb62ac63313d63dbfd3a6 \
-sha256
1325c9ade812679e444b54b3e3faf79c1239254947a81fe48ab342043073eae2
+master_siteshttps://github.com/ocamllabs/ocaml-ctypes/archive/
+distname${version}
Consider using the github portgroup instead of doing what it does manually.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
extract multiple files with formats
Is something like this possible: distfiles file1.gz file2.zip Regards, Bradley Giesbrecht (pixilla) signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: extract multiple files with formats
vim might be a good example on this. distfiles-appendvim-7.4.16-fc19-breakindent.patch:breakindent On Aug 26, 2014, at 13:27, Bradley Giesbrecht pixi...@macports.org wrote: Is something like this possible: distfiles file1.gz file2.zip Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: extract multiple files with formats
On Aug 26, 2014, at 1:27 PM, Bradley Giesbrecht pixi...@macports.org wrote: Is something like this possible: distfiles file1.gz file2.zip To my knowledge, no. Fetching will work fine, but the extract phase assumes that all elements of extract.only (defaulting to all distfiles) are the same kind of archive and runs extract.cmd on all of them. In a prior version of the rust Portfile, I worked around this by trimming extract.only and using an unwieldy post-extract phase. http://trac.macports.org/browser/trunk/dports/lang/rust/Portfile?rev=123558 vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: extract multiple files with formats
On Aug 26, 2014, at 1:48 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: vim might be a good example on this. distfiles-appendvim-7.4.16-fc19-breakindent.patch:breakindent This only works for vim because extract.only is explicitly restricted to the tarball. Base downloads the patches and subsequently ignores them. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: extract multiple files with formats
On Aug 26, 2014, at 12:11 PM, Lawrence Velázquez lar...@macports.org wrote:
On Aug 26, 2014, at 1:48 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
vim might be a good example on this.
distfiles-appendvim-7.4.16-fc19-breakindent.patch:breakindent
This only works for vim because extract.only is explicitly restricted to the
tarball. Base downloads the patches and subsequently ignores them.
I'm doing this:
...
distfiles GeoLite2-City.mmdb.gz GeoLite2-City-CSV.zip
extract {
extract.args'${distpath}/[lindex ${distfiles} 0]'
extract.suffix .gz
extract.post_args | cat ${worksrcpath}/GeoLite2-City.mmdb
command_exec extract
use_zip yes
portextract::extract_start
extract.args'${distpath}/[lindex ${distfiles} 1]'
command_exec extract
}
...
and wishing tags worked here[1]:
...
distfiles GeoLite2-City.mmdb.gz:f1 GeoLite2-City-CSV.zip:f2
extract.suffix.gz:f1
extract.post_args| cat ${worksrcpath}/GeoLite2-City.mmdb:f1
use_zipyes:f2
...
[1] https://guide.macports.org/#reference.phases.fetch
Regards,
Bradley Giesbrecht (pixilla)
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Configuration and environment check command (was: Re: [124047] trunk/base)
On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote: However, I am not too happy with naming the command 'port doctor'. Many other commands used with port(1) are verbs, but using this as a verb carries the wrong message. I know where the naming comes from, but there is no need to match any other terminology and we should rather define our own coherent names. My proposal would be to rename this to 'port selfcheck' instead. I second the proposal. Selfcheck is a bit awkward, but it does parallel selfupdate nicely. Anything would be better than doctor, which is transparently derivative. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Configuration and environment check command (was: Re: [124047] trunk/base)
On Aug 26, 2014, at 4:54 PM, Lawrence Velázquez lar...@macports.org wrote: On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote: However, I am not too happy with naming the command 'port doctor'. Many other commands used with port(1) are verbs, but using this as a verb carries the wrong message. I know where the naming comes from, but there is no need to match any other terminology and we should rather define our own coherent names. My proposal would be to rename this to 'port selfcheck' instead. I second the proposal. Selfcheck is a bit awkward, but it does parallel selfupdate nicely. Anything would be better than doctor, which is transparently derivative. +1 port selfcheck alt: port maintenance Regards, Bradley Giesbrecht (pixilla) signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Configuration and environment check command (was: Re: [124047] trunk/base)
On Aug 25, 2014, at 6:35 AM, Rainer Müller rai...@macports.org wrote: However, I am not too happy with naming the command 'port doctor'. Many other commands used with port(1) are verbs, but using this as a verb carries the wrong message. I know where the naming comes from, but there is no need to match any other terminology and we should rather define our own coherent names. My proposal would be to rename this to 'port selfcheck' instead. I second the proposal. Selfcheck is a bit awkward, but it does parallel selfupdate nicely. Anything would be better than doctor, which is transparently derivative. 'port selfexam' ? 'port sefldiagnose' ? Just kidding, but they play on the medical theme... Craig ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Configuration and environment check command
On Aug 26, 2014, at 7:33 PM, Craig Treleaven wrote: On Aug 25, 2014, at 6:35 AM, Rainer Müller wrote: However, I am not too happy with naming the command 'port doctor'. Many other commands used with port(1) are verbs, but using this as a verb carries the wrong message. I know where the naming comes from, but there is no need to match any other terminology and we should rather define our own coherent names. My proposal would be to rename this to 'port selfcheck' instead. I second the proposal. Selfcheck is a bit awkward, but it does parallel selfupdate nicely. Anything would be better than doctor, which is transparently derivative. 'port selfexam' ? 'port sefldiagnose' ? Just kidding, but they play on the medical theme... Without remembering exactly what the current doctor does, I was going to suggest diagnose. Personally I want to avoid reusing the self prefix because it means if you want to run selfupdate you then have to at least type sudo port selfu; currently, it's possible to shorten it to sudo port self. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Configuration and environment check command
On 2014-8-27 15:16 , Ryan Schmidt wrote: On Aug 26, 2014, at 7:33 PM, Craig Treleaven wrote: On Aug 25, 2014, at 6:35 AM, Rainer Müller wrote: However, I am not too happy with naming the command 'port doctor'. Many other commands used with port(1) are verbs, but using this as a verb carries the wrong message. I know where the naming comes from, but there is no need to match any other terminology and we should rather define our own coherent names. My proposal would be to rename this to 'port selfcheck' instead. I second the proposal. Selfcheck is a bit awkward, but it does parallel selfupdate nicely. Anything would be better than doctor, which is transparently derivative. 'port selfexam' ? 'port sefldiagnose' ? Just kidding, but they play on the medical theme... Without remembering exactly what the current doctor does, I was going to suggest diagnose. Personally I want to avoid reusing the self prefix because it means if you want to run selfupdate you then have to at least type sudo port selfu; currently, it's possible to shorten it to sudo port self. Also most of the checks are on the environment, not MacPorts itself. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
