Re: [144262] trunk/dports/lang/py-htmldocs/Portfile
On 8 January 2016 at 01:47, Ryan Schmidt wrote: > On Jan 7, 2016, at 12:12 PM, Eric A. Borisch wrote: > >> Bringing this back to the original point, it looks like there was some >> discussion (I think) in this thread of making alocation (possibly >> integrated in terms of access accounts with svn commit access) >> available to store a 'snapshot' of a 'distfile' for instances like >> this (where the source performs nightly refreshes of the tarball >> without version information in the name.) >> >> So is that going to happen (soon), or is the desire I bake something >> else up (drafting off curl-ca-bundle or graphviz-devel) for now? > > I have no plans to implement an arbitrary-file-hosting infrastructure for > MacPorts in the near future, and lots of other things I need to be working > on. You should solve the problem in the portfile. One can put a file basically *anywhere* on the web, wait until it gets mirrored and then safely remove both the file and the URL. Users would then get the file from MacPorts mirror. In the case of py-htmldocs you could probably commit a Portfile with correct checksums for that day and the corresponding subdir (maybe with a date if the filename doesn't change). Once the file gets mirrored, just remove the URL of the file and make sure that all users will get the file from the MacPorts mirror from that moment on. Once you decide to switch to a newer version, repeat the process (uncomment the URL, correct the checksums, commit, wait for the mirror, comment out the URL, commit). Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
build.args
Hi all, Is there a way to get the value of build.args in a Portfile? I would like to do something like pre-test { test.args-append ${build.args} } but there is no such variable. David ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [144426] trunk/doc-new/guide/xml/portfile-tcl.xml
Oops and thanks for the further clarifications. I have just updated it. David On Fri, Jan 8, 2016 at 5:02 PM, Joshua Rootwrote: > > Revision: 144426 > > https://trac.macports.org/changeset/144426 > > Author: dstrubbe at macports.org > > Date: 2016-01-08 12:16:33 -0800 (Fri, 08 Jan 2016) > > Log Message: > > --- > > doc-new: Add comments on locale in reinplace. > > > > Modified Paths: > > -- > > trunk/doc-new/guide/xml/portfile-tcl.xml > > > > Modified: trunk/doc-new/guide/xml/portfile-tcl.xml > > === > > --- trunk/doc-new/guide/xml/portfile-tcl.xml 2016-01-08 19:39:53 UTC > (rev 144425) > > +++ trunk/doc-new/guide/xml/portfile-tcl.xml 2016-01-08 20:16:33 UTC > (rev 144426) > > @@ -275,7 +275,9 @@ > >the command with the replacement text, in all files > >specified. > > > > - Use -locale to set the locale > > + Use -locale to set the locale. For example, > locale -C > > + if a non-ASCII file is being modified (which may otherwise > give the error > > + "sed: RE error: illegal byte sequence"). > > Setting a locale is not needed for all non-ASCII files, just non-UTF-8 > ones (as the default locale is "en_US.UTF-8"). It may also be worth > mentioning that using "C" will only allow ASCII characters to be > processed correctly by the reinplace, so if you need it to work on > non-ASCII characters you need to set a locale with the correct charset > for the file, e.g. "en_US.ISO8859-1". > > Also, it should be "-locale C" not "locale -C". > > - Josh > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
[144426] trunk/doc-new/guide/xml/portfile-tcl.xml
> Revision: 144426 > https://trac.macports.org/changeset/144426 > Author: dstrubbe at macports.org > Date: 2016-01-08 12:16:33 -0800 (Fri, 08 Jan 2016) > Log Message: > --- > doc-new: Add comments on locale in reinplace. > > Modified Paths: > -- > trunk/doc-new/guide/xml/portfile-tcl.xml > > Modified: trunk/doc-new/guide/xml/portfile-tcl.xml > === > --- trunk/doc-new/guide/xml/portfile-tcl.xml 2016-01-08 19:39:53 UTC (rev > 144425) > +++ trunk/doc-new/guide/xml/portfile-tcl.xml 2016-01-08 20:16:33 UTC (rev > 144426) > @@ -275,7 +275,9 @@ >the command with the replacement text, in all files >specified. > > - Use -locale to set the locale > + Use -locale to set the locale. For example, locale > -C > + if a non-ASCII file is being modified (which may otherwise give > the error > + "sed: RE error: illegal byte sequence"). Setting a locale is not needed for all non-ASCII files, just non-UTF-8 ones (as the default locale is "en_US.UTF-8"). It may also be worth mentioning that using "C" will only allow ASCII characters to be processed correctly by the reinplace, so if you need it to work on non-ASCII characters you need to set a locale with the correct charset for the file, e.g. "en_US.ISO8859-1". Also, it should be "-locale C" not "locale -C". - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [144262] trunk/dports/lang/py-htmldocs/Portfile
Another solution would be a PR with a patch for https://github.com/python/docsbuild-scripts/blob/master/build_docs.py to add versions, I guess. Russell On 08/01/16 09:11, Mojca Miklavec wrote: On 8 January 2016 at 01:47, Ryan Schmidt wrote: On Jan 7, 2016, at 12:12 PM, Eric A. Borisch wrote: Bringing this back to the original point, it looks like there was some discussion (I think) in this thread of making alocation (possibly integrated in terms of access accounts with svn commit access) available to store a 'snapshot' of a 'distfile' for instances like this (where the source performs nightly refreshes of the tarball without version information in the name.) So is that going to happen (soon), or is the desire I bake something else up (drafting off curl-ca-bundle or graphviz-devel) for now? I have no plans to implement an arbitrary-file-hosting infrastructure for MacPorts in the near future, and lots of other things I need to be working on. You should solve the problem in the portfile. One can put a file basically *anywhere* on the web, wait until it gets mirrored and then safely remove both the file and the URL. Users would then get the file from MacPorts mirror. In the case of py-htmldocs you could probably commit a Portfile with correct checksums for that day and the corresponding subdir (maybe with a date if the filename doesn't change). Once the file gets mirrored, just remove the URL of the file and make sure that all users will get the file from the MacPorts mirror from that moment on. Once you decide to switch to a newer version, repeat the process (uncomment the URL, correct the checksums, commit, wait for the mirror, comment out the URL, commit). Mojca ___ 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: [144360] trunk/dports/gnome
On Jan 6, 2016, at 9:44 PM, dev...@macports.org wrote: > > Revision > 144360 > Author > dev...@macports.org > Date > 2016-01-06 19:44:30 -0800 (Wed, 06 Jan 2016) > Log Message > > py27-gda: remove obsolete port, no dependents, no replacement. Looks like you also updated gnotime to 2.4.0, possibly unintentionally. > Modified Paths > > • trunk/dports/gnome/gnotime/Portfile > Removed Paths > > • trunk/dports/gnome/py27-gda/ > Diff > > Modified: trunk/dports/gnome/gnotime/Portfile (144359 => 144360) > > --- trunk/dports/gnome/gnotime/Portfile 2016-01-07 03:35:12 UTC (rev > 144359) > +++ trunk/dports/gnome/gnotime/Portfile 2016-01-07 03:44:30 UTC (rev > 144360) > > @@ -4,7 +4,7 @@ > > PortSystem 1.0 > > > > name gnotime > > -version 2.1.7 > > +version 2.4.0 > > description A GNOME project manager. > > long_descriptionGnoTime is a combination stop-watch, diary, \ > > consultant billing system and project manager. \ > > @@ -18,7 +18,10 @@ > > platformsdarwin > > homepage http://gttr.sourceforge.net/ > master_sitessourceforge:gttr > > -checksumsmd5 f5543b00fb2646e7d2d1619a2aeed31d > > + > +checksums rmd160 a0963cad9547c9b25f2ee6280c211a7fcb87e4d2 \ > +sha256 > a1bf1389829e5795016cc49810c8be80f9bbccb5d56e97f00efb0718559a539b > + > > depends_buildport:pkgconfig > > depends_lib bin:guile:guile port:libgtkhtml port:libgnome port:libgnomeui > > configure.cppflags-append "-L${prefix}/lib" ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [144336] trunk/dports/science/silo/Portfile
On Jan 6, 2016, at 1:21 PM, dstru...@macports.org wrote: > > Revision > 144336 > Author > dstru...@macports.org > Date > 2016-01-06 11:21:10 -0800 (Wed, 06 Jan 2016) > Log Message > > silo: Use compilers portgroup for Fortran variants. Clarify meaning in > description. Update livecheck. Remove irrelevant comment. Add caution about > MPI with HDF5. Well, the comment was relevant in that it documented the error message one got when ccache was used, thus explaining why it had been disabled for this port. > Modified Paths > > • trunk/dports/science/silo/Portfile > Diff > > Modified: trunk/dports/science/silo/Portfile (144335 => 144336) > -# Makefile:152: *** missing separator. Stop. > +compilers.choosefc f77 f90 > +compilers.setup > + > configure.ccacheno ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: build.args
On 2016-1-9 08:21 , David Strubbe wrote: > Hi all, > > Is there a way to get the value of build.args in a Portfile? I would > like to do something like > > pre-test { >test.args-append ${build.args} > } > > but there is no such variable. The variable doesn't exist if it has not been set. In that case, there is of course no value to get. You can test for its existence with [exists build.args]. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [144262] trunk/dports/lang/py-htmldocs/Portfile
On 2016-1-8 05:12 , Eric A. Borisch wrote: > Bringing this back to the original point, it looks like there was some > discussion (I think) in this thread of making alocation (possibly > integrated in terms of access accounts with svn commit access) > available to store a 'snapshot' of a 'distfile' for instances like > this (where the source performs nightly refreshes of the tarball > without version information in the name.) > > So is that going to happen (soon), or is the desire I bake something > else up (drafting off curl-ca-bundle or graphviz-devel) for now? I wonder if sourceforge's rules would allow making another project called something like "macports-distfiles" and giving all our committers the ability to add files to it. From a quick look at the terms of use, it appears that uploaded content just needs to have a license "compliant with the Open Source Initiative (“OSI”)’s Open Source Definition". - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev