This is really a non-issue. The intent of the MD5 in the Portfile is
easily identify when a source archive was corrupted during download,
or when a 404 file was obtained instead of a source archive. It's not
about security, it's about providing a checksum for data -- and to
that effect
Hi,
I'm the upstream maintainer of tuxmath, and I also want to add it to MacPorts
and become the port maintainer for it. So, regarding checksums, I take it
that it would be best (from the point of view of MacPorts, and probably
anyone else who cares to verify that they are getting unaltered
Ryan Schmidt wrote:
Of course, this won't make Rainer happy. :-)
http://trac.macosforge.org/projects/macports/browser/trunk/dports/
editors/vim/files/patchlist?rev=34037
Look at all them pretty md5s...
These md5s are released upstream [1] and I just use them. Of course I
now could also
Hi Blair,
If Maintainers think so, that's fine with me.
I just guessed 72 hours are not practical to accept for maintainers.
On 2/16/08, Blair Zajac [EMAIL PROTECTED] wrote:
js wrote:
Hi,
MacPorts Guide says
The maintainer should apply the patches and close the ticket within 72
# Moving from Trac ticket #14342
No, py25-foo can have different dependencies than py-foo. I don't know
what you wanted to tell us with this.
I meant if we would change python24 to drop some standard modules like
the current python25 port does, py-foo and py25-foo's dependencies
would be the
Hey guys!
The guide is advancing so nicely that I'm afraid we've hit the point
when it's maybe becoming a tad too large for a single page, wouldn't
y'all think?
Every time I have to load a section of the guide a have a moment of
hesitation in fear of loading such a
On Feb 16, 2008, at 05:41, David Bruce wrote:
I'm the upstream maintainer of tuxmath, and I also want to add it
to MacPorts
and become the port maintainer for it. So, regarding checksums, I
take it
that it would be best (from the point of view of MacPorts, and
probably
anyone else
The unison port has recently been upgraded from 2.13 to 2.27. The
problem is that the protocol has changed between these versions,
and unison 2.13 can't talk to unison 2.27:
http://trac.macosforge.org/projects/macports/ticket/14172
The only solution that can work in every case (because users
On Feb 11, 2008, at 17:38, David Bruce wrote:
After some study of the guide (as well as several existing
Portfiles), I've
taken my first stab at writing a Portfile for tuxmath and submitted
it as
trac ticket #14279. How can I start testing it to see what needs
to be
fixed?
Tuxmath
Ryan Schmidt wrote:
Rainer has commented on your ticket so once you review those changes
I imagine he'll commit it.
Yes, that was my intention :-)
I saw your earlier message but did not have time to deal with it.
Sometimes we're just short on time and tickets get forgotten.
That's often
10 matches
Mail list logo
