On 2013-11-15 05:43 , Peter Danecek wrote:
>
> On Oct 23, 2013, at 19:15 , Joshua Root wrote:
>
>> There certainly isn't any mention of share/examples in hier(7) or the
>> FHS. I don't know why it's in porthier(7), it's been there since the
>> file was first checked in.
>
> (1) Following this a
Hi Jeremy and others,
Do you have any suggestions regarding my submitted ports xcrysden (
https://trac.macports.org/ticket/41320) and mesa702 (
https://trac.macports.org/ticket/41319)? I understand it is undesirable to
introduce an old version of mesa, but I am not sure how to investigate the
inco
On Nov 14, 2013, at 2:53 PM, Peter Danecek wrote:
> in an attempt to comply with licensing (which the original package might fail
> to do), I add some doc files. I have put them into ${portpath}/files and than
> copy them directly into destroot.
Where are you getting these files coming from?
Definitely nice to have updated GNOME packages! Thanks!
What about these wiki pages?
https://trac.macports.org/wiki/GNOME
https://trac.macports.org/wiki/GNOMEPackageStatus
Is there any script to update the tables in the latter?
On 2013-11-14 00:25, Eric Gallager wrote:
> Yeah, I agree, it's nic
On 2013-11-14 20:53, Peter Danecek wrote:
> xinstall -m 644 -W ${portpath}/files \
^
${filespath}
It's just a shorter alias of the same path.
> It works, but it might not be the intended use. Is this approach okay?
Yes.
>
Hi all,
in an attempt to comply with licensing (which the original package might fail
to do), I add some doc files. I have put them into ${portpath}/files and than
copy them directly into destroot.
post-destroot {
[…]
set dest_doc ${destroot}${prefix}/share/doc
xinstall -d ${dest_doc}
Just a short follow up on this, because I still not clear what is considered
"correct".
On Oct 23, 2013, at 19:15 , Joshua Root wrote:
> On 2013-10-24 03:24 , Blair Zajac wrote:
>> I disagree, I don't find $prefix/share/examples natural at all, maybe
>> because Linux doesn't have this director
Thanks for this hint!
Probably it is best, to be more explicit in the subject.
~petr
On Nov 14, 2013, at 18:10 , Mojca Miklavec
wrote:
> PS: I would suggest to include the port name in the subject, but then
> again I'm not sure about the balance between the number of committers
> which would
In the gnuradio port, I use an "eval [subst {" to handle multiple Python
variants.
"s" is the "pythonXY" XY suffix, so "26" or "27" as examples.
I want to be able to use either py*-pyqt4 or py*-pyqt4-devel, so I add:
depends_lib-append
path:share/qt4/plugins/designer/libpy${s}qt4.dylib:py${s}-py
Hi committers,
the ticket (https://trac.macports.org/ticket/39378) is around for about 5 month
and I see no reaction from the maintainer.
I provided some patches, so could anyone have a look at this?
Thanks!
~petr
smime.p7s
Description: S/MIME cryptographic signature
___
[Sorry, I didn't finish before my mail program sent ... let's try this
again ...]
I have a few ports which need access to various of the *FLAGS during the
build stage, as created during the configure stage. I've read through
the code in port1.0/portconfigure.tcl:configure_main, and it seems like
On Nov 14, 2013, at 16:35 , Ryan Schmidt wrote:
>
> On Nov 14, 2013, at 08:36, Joshua Root wrote:
>
>> But anyway, the main
>> purpose of this mechanism is to allow the lists of mirrors to be updated
>> in one place, so there really isn't much point when there's just the one
>> URL.
>
> The m
I have a few ports which need access to various of the *FLAGS, as
created during the configure stage. I've read through the code in
port1.0/portconfigure.tcl: configure_main, and it seems like it goes
through the process of creating the flags from those set mainly in
configure.*, pushed into the c
On Nov 14, 2013, at 08:36, Joshua Root wrote:
> But anyway, the main
> purpose of this mechanism is to allow the lists of mirrors to be updated
> in one place, so there really isn't much point when there's just the one
> URL.
The main purpose of the mechanism is to provide a central place to rec
Sorry to Joshua, I missed to CC the list!
On Nov 14, 2013, at 15:36 , Joshua Root wrote:
> On 2013-11-15 01:22 , Peter Danecek wrote:
>>
>> Hi all,
>>
>> for curiosity I tried to put this into a Portfile the following:
>>
>> master_sitespypi:PyODE
>>
>>
>> This would not work,
On 2013-11-15 01:22 , Peter Danecek wrote:
>
> Hi all,
>
> for curiosity I tried to put this into a Portfile the following:
>
> master_sitespypi:PyODE
>
>
> This would not work, but I wonder why or if this could not be possible? It
> would then resolve to:
>
> http://pypi
Hi all,
for curiosity I tried to put this into a Portfile the following:
master_sitespypi:PyODE
This would not work, but I wonder why or if this could not be possible? It
would then resolve to:
http://pypi.python.org/packages/source/P/PyODE/PyODE-1.2.1.tar.gz
or
On Nov 14, 2013, at 06:55, Thomas Robitaille wrote:
> Thanks for making the changes! Just so I understand, this will (after
> the next version) no longer use the official tar file, but instead the
> tar file produced from the git tag? In that case, which checksums
> should I enter next time?
“Re
On Nov 14, 2013, at 06:44, Ryan Schmidt wrote:
> On Nov 14, 2013, at 06:42, Thomas Robitaille wrote:
>
>> I'm not sure how to use the github portgroup (it isn't described in
>> section 5.9 of the guide). Do you have a simple example you could show
>> me? (alternatively, feel free to fix it up).
On Nov 14, 2013, at 06:42, Thomas Robitaille wrote:
> Hi Ryan,
>
> I'm not sure how to use the github portgroup (it isn't described in
> section 5.9 of the guide). Do you have a simple example you could show
> me? (alternatively, feel free to fix it up).
I would usually say: read the comments in
On Nov 14, 2013, at 06:37, robitai...@macports.org wrote:
> Revision
> 113356
> Author
> robitai...@macports.org
> Date
> 2013-11-14 04:37:07 -0800 (Thu, 14 Nov 2013)
> Log Message
>
> erfa: updated to 1.0.1 and added to github portgroup
> Modified Paths
>
> • trunk/dports/science/erfa/Po
On Nov 14, 2013, at 06:32, Peter Danecek wrote:
> Anyway, the license I am looking at is Creative Common Attribution 3.0
> (http://creativecommons.org/licenses/by/3.0).
> Is "CC-BY-3.0" the appropriate/correct abbreviation?
The format of a license specification must be:
licensename (any vers
Thanks Ryan,
maybe I was recalling this, not sure any more.
Anyway, the license I am looking at is Creative Common Attribution 3.0
(http://creativecommons.org/licenses/by/3.0).
Is "CC-BY-3.0" the appropriate/correct abbreviation?
I understand it should be distributable, it's not binary thoug
On Nov 13, 2013, at 11:49, dev...@macports.org wrote:
> Revision
> 11
> Author
> dev...@macports.org
> Date
> 2013-11-13 09:49:19 -0800 (Wed, 13 Nov 2013)
> Log Message
>
> gdm: merge version 3.10.0.1 from GNOME-3 test branch.
> Modified Paths
>
> • trunk/dports/gnome/gdm/Portfile
>
On Nov 14, 2013, at 05:39, Peter Danecek wrote:
> I believe to have already seen such a list, probably somewhere in the Wiki,
> but I now cannot find it.
> What about linking this list from the Guide? I guess 5.1 -> license would be
> the right place.
The only list of licenses known to MacPort
Hi all,
I believe to have already seen such a list, probably somewhere in the Wiki, but
I now cannot find it.
What about linking this list from the Guide? I guess 5.1 -> license would be
the right place.
Thanks!
~petr
smime.p7s
Description: S/MIME cryptographic signature
26 matches
Mail list logo
