On 11/08/2014 04:26 PM, Lawrence Velázquez wrote:
> On Nov 8, 2014, at 2:01 AM, Andrea D'Amore wrote:
>
>> The rule of thumb is to start the commit line with the component, e.g.
>> "port gdal" for gdal and "base" for change in base. Also "maintainer
>> timeout" should be specified, I put the main
On Nov 8, 2014, at 2:01 AM, Andrea D'Amore wrote:
> The rule of thumb is to start the commit line with the component, e.g.
> "port gdal" for gdal and "base" for change in base. Also "maintainer
> timeout" should be specified, I put the maintenance info at the end of
> the message.
>
> We could e
On Tue, Nov 4, 2014 at 1:44 PM, petr <9...@ingv.it> wrote:
> I'd like to propose to start commit messages with the port name. This helps
> very much to read them for example in the Timeline.
It's already the case, I remember being pointed at this several years ago.
The rul
Vincent Habchi writes:
> Ciao Petr,
>
>> I'd like to propose to start commit messages with the port name. This helps
>> very much to read them for example in the Timeline.
>>
>> For example:
>>
>> https://trac.macports.org/changeset/127794
Ciao Petr,
> I'd like to propose to start commit messages with the port name. This helps
> very much to read them for example in the Timeline.
>
> For example:
>
> https://trac.macports.org/changeset/127794 -- Correct various bugs. Bump to
> revision 1.
> https:
Hi Vincent,
I'd like to propose to start commit messages with the port name. This helps
very much to read them for example in the Timeline.
For example:
https://trac.macports.org/changeset/127794 -- Correct various bugs. Bump to
revision 1.
https://trac.macports.org/changeset/127795 --
On Oct 18, 2014, at 10:59 PM, Mark Brethen wrote:
> At this point I issued 'sudo port clean reduce-csl' and everything was ok,
> but should portfiles anticipate such an event?
We generally consider interrupted builds to be user error. If we eventually
decide that we should clean up preemptivel
On Oct 18, 2014, at 9:59 PM, Mark Brethen wrote:
> On Oct 18, 2014, at 9:50 PM, Ryan Schmidt wrote:
>
>> On Oct 18, 2014, at 9:35 PM, Mark Brethen wrote:
>>
>>> However an issue I've found is that if the install process is interrupted,
>>> a subsequent re-issue of 'port install reduce' will fai
On Oct 18, 2014, at 9:50 PM, Ryan Schmidt wrote:
>
> On Oct 18, 2014, at 9:35 PM, Mark Brethen wrote:
>
>> if {${name} eq ${subport}} {
>> supported_archs noarch
>> distfiles
>> archive_sites
>>
>> use_configure no
>>
>> build {}
>>
>> depends_build-append\
>>
On Oct 18, 2014, at 9:35 PM, Mark Brethen wrote:
> if {${name} eq ${subport}} {
>supported_archs noarch
>distfiles
>archive_sites
>
>use_configure no
>
>build {}
>
>depends_build-append\
>port:reduce-common\
>port:reduce-csl\
>port:re
On Oct 13, 2014, at 4:03 PM, Ryan Schmidt wrote:
> All ports must install at least one file. You can look at other metaports to
> see what they do. Typically they create a file called README and put either a
> placeholder message or the port's description into it.
>
> You'll also want to set
On Oct 13, 2014, at 9:44 AM, Mark Brethen wrote:
>
> On Oct 13, 2014, at 7:41 AM, Brandon Allbery wrote:
>
>> On Mon, Oct 13, 2014 at 8:33 AM, Mark Brethen wrote:
>>> If a user tries to install port ${name} how should this be handled?
>>
>> That depends
On Oct 13, 2014, at 7:41 AM, Brandon Allbery wrote:
> On Mon, Oct 13, 2014 at 8:33 AM, Mark Brethen wrote:
> If a user tries to install port ${name} how should this be handled?
>
> That depends on what exactly you're trying to do. Obvious possibilities
> include instal
On Mon, Oct 13, 2014 at 8:33 AM, Mark Brethen
wrote:
> If a user tries to install port ${name} how should this be handled?
That depends on what exactly you're trying to do. Obvious possibilities
include installing all subports or some common subset thereof, via
dependencies possibly
My portfile uses subports to install the various sources in an svn repository.
The port name isn't used at all. Are there examples of this?
If a user tries to install port ${name} how should this be handled?
Mark
___
macports-dev mailing
2013/12/28 Rainer Müller :
> On 2013-12-26 19:25, Davide Liessi wrote:
>> can you please review this?
>>
>> https://trac.macports.org/ticket/40831
>
> I committed the change to the github port group.
> http://trac.macports.org/changeset/115223
I reopened the ticket, since the applied change breaks
On 2013-12-26 19:25, Davide Liessi wrote:
> Dear MacPorts developers,
> can you please review this?
>
> https://trac.macports.org/ticket/40831
I committed the change to the github port group.
http://trac.macports.org/changeset/115223
Rainer
___
macport
Dear MacPorts developers,
can you please review this?
https://trac.macports.org/ticket/40831
Merry Christmas to you all.
Davide Liessi
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports
Dear MacPorts developers,
can you please review the patch I submitted at
https://trac.macports.org/ticket/40831?
I would appreciate any comments.
Best wishes.
Davide Liessi
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.maco
On Sep 26, 2009, at 22:21, Scott Haneda wrote:
Thanks for all the info, very interesting. I am glad this came up,
as there is a pretty big poop fest over on the twitter dev mailing
list about their user_id breaking into 64 bit territory.
They return JSON for most of everything, and most d
Thanks for all the info, very interesting. I am glad this came up, as
there is a pretty big poop fest over on the twitter dev mailing list
about their user_id breaking into 64 bit territory.
They return JSON for most of everything, and most devs are using php5,
which most hosts are buildin
On Sun, Sep 27, 2009 at 7:27 AM, Ryan Schmidt wrote:
> Why would anybody want MySQL 5.0.x now that 5.1.x is available?
>
> We already have a mysql4 port which provides 4.1.x, though I expect to
> remove it next year after 4.1.x has been end-of-life'd.
>
> I am in the process of removing the mysql3
On Sep 26, 2009, at 17:16, Mark Hattam wrote:
MySQL continues to refer to both 5.0.x and 5.1.x as both being GA
releases
http://dev.mysql.com/downloads/mysql/5.0.html
and
http://dev.mysql.com/downloads/mysql/5.1.html
And there appears to be no end-of-life statement about 5.0 apart
from th
On 26 Sep 2009, at 17:45, Ryan Schmidt wrote:
On Sep 26, 2009, at 04:53, Akira Kitada wrote:
I realized mysql5 and mysql5-server ports are still pointing to
5.0.x,
ex-GA release of MySQL
and need to install mysql5-devel and mysql5-server-devel for 5.1.x,
the current GA release.
If I unders
On Sep 26, 2009, at 14:24, Scott Haneda wrote:
Question of curiosity. Why does MacPorts needs to be able to build
a UB? MacPorts builds on the machine it is intended to use. I am
not aware of many desiring to copy a binary from one machine to the
other, and that would be a lot of work wit
On 2009-9-27 05:24, Scott Haneda wrote:
> Question of curiosity. Why does MacPorts needs to be able to build a
> UB? MacPorts builds on the machine it is intended to use. I am not
> aware of many desiring to copy a binary from one machine to the other,
> and that would be a lot of work with all t
Question of curiosity. Why does MacPorts needs to be able to build a
UB? MacPorts builds on the machine it is intended to use. I am not
aware of many desiring to copy a binary from one machine to the other,
and that would be a lot of work with all the man pages and other parts
that may co
Hi,
I realized mysql5 and mysql5-server ports are still pointing to 5.0.x,
ex-GA release of MySQL
and need to install mysql5-devel and mysql5-server-devel for 5.1.x,
the current GA release.
If I understand correctly, -devel suffix denotes that the port is a
development version
but this case, it a
On Sep 26, 2009, at 04:53, Akira Kitada wrote:
I realized mysql5 and mysql5-server ports are still pointing to 5.0.x,
ex-GA release of MySQL
and need to install mysql5-devel and mysql5-server-devel for 5.1.x,
the current GA release.
If I understand correctly, -devel suffix denotes that the port
On Jan 3, 2007, at 6:08 PM, Kevin Ballard wrote:
I've CC'ed the dev list - anybody have any thoughts on modifying
the version-matching regex here? And does anybody know of any other
locations where the version is matched against a regex?
Final thoughts: I just remembered that this same routi
It appears, from looking at the source, that the registry only
matches the following characters in the version:
-
_
a-z
A-Z
0-9
.
Perhaps this should be modified. I would suggest matching everything
besides, say, a space here. Everything else should be fine, because
the routine
31 matches
Mail list logo
