Thanks, Patrick, I don't imagine it will be difficult to incorporate any
changes you made.
-LG
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Thanks for the tip. I've created a ticket for it
(http://trac.macports.org/ticket/29822).
I don't have experience using direct mode. Is it something I can
safely switch to just by editing macports.conf, or would it be better
for me to reinstall from scratch?
--
Larry Gi
dency on p5-lwp-protocol-https.
Right now, the new p5-libwww-perl defaults to a +ssl variant that
automatically includes this dependency, but adding it to your port now
will keep it working when the variant stops being the default
(someday).
--
Lar
bitcoind is not the usual ends-with-d daemon. It can act both as a
daemon and a client, and I think it's intended to be run as a normal
user and not root.
-L2G
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/ma
or one reason or another, MacPorts will think there are no
other Sourceforge sources to try and it will give up. Right now I
think it goes through multiple Sourceforge mirrors until either it
finds the file or it gives up after trying all mirrors. Is that right?
--
Larry Gilber
On Mon, May 16, 2011 at 6:33 PM, Vincent Lefevre
wrote:
> Should p5-libvorbis-perl be removed?
It seems to me like a reasonable thing to do. It's out-of-date, as you
say, and it appears that no other ports depend on it. You might want
to wait for another opinion besides mine, though.
-
Does anyone have any comment on the change I've proposed in ticket #28393?
http://trac.macports.org/ticket/28393
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinf
t access?
And we've got a new broken port from the same committer: games/rott.
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
I've made an experimental implementation of depends_test that others might
want to play with. Is somewhere under
http://svn.macports.org/repository/macports/users/l2g the best place to put
it?
--
Larry Gilbert (L2G)
___
macports-dev mailing
n the past
> months with comments that certain dependencies should really be depend_test
> if we had it.
Is that something that would warrant bumping the PortSystem version
from 1.0 to, say, 1.1? Or is the PortSystem version meant for some
other
On Tue, Mar 29, 2011 at 3:03 PM, Jeremy Lavergne
wrote:
> Regardless of what the replaced_by is set to, let's kill it based on the
> original duration and not reset it.
Sounds good to me!
--
Larry Gilbert (L2G)
___
macports-dev m
ay be deleted from the repository. But what happens if it is edited again,
as in this case? Does that reset the clock, so to speak? Or is it still okay
to delete?
(What really throws me is that at the time of r72394, it seems like it was
already a candidate for deletion.)
--
Larry Gilbert
On Sun, Mar 27, 2011 at 1:31 PM, Joshua Root wrote:
> Seems perfectly reasonable if you have verified that they are only used
> at build time.
I deactivated all of its dependencies (except for perl5, of course),
and it still worked as expected.
--
Larry Gilber
On Sun, Mar 27, 2011 at 3:33 AM, Chris Scharver wrote:
>
> Yeah, that's my bad for not combing through the tcl patch in enough detail.
> I corrected this in r77288.
>
>
I'm at least as much to blame since I created the original patch. I will
take the advice to heart
It looks like the dependencies in p5-time-y2038 are really just build
dependencies, so I've proposed changes to the portfile to reflect that:
https://trac.macports.org/ticket/28874
Since I'm still a rookie committer, I'd welcome a second opinion.
Thanks!
--
Lar
On Thu, Mar 10, 2011 at 9:37 AM, Bradley Giesbrecht
wrote:
> Where are the guidelines you are referring to located?
The ones I'm aware of are under
http://trac.macports.org/wiki/NewCommittersGuide, "Port Committer
Responsibilities," number 8.
--
I was doing the right thing by making these perl5 ports consistent
with the others and with the guidelines in the MacPorts Guide ("never
use depends_lib in ports belonging to a PortGroup or it will overwrite
the default library dependencies").
http://trac.macports.org/ticket/28650#co
On Sat, Mar 5, 2011 at 11:14 PM, Ryan Schmidt wrote:
>
> Sounds ok to me. Thanks for finding this problem and taking the initiative to
> fix it. :)
I give Brad the credit for the finding!
--
Larry Gilbert (L2G)
___
macports-dev mailing list
for this
and any other ports that you may have maintained before?
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
ve
others the chance to speak up in case I'm about to do something
horribly wrong!
Thanks!
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On Sun, Feb 27, 2011 at 7:11 AM, Michael Klein
wrote:
> Can someone with commit rights please commit and close #22457?
I'll take a look at it.
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.
hese today.
I for one will be looking forward to them!
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
I could have sworn I saw a place where the portfile "license" field was
documented, but I'll be darned if I can find it now, even with a search
engine. Does anyone else know where it is? Sorry if I'm being daft.
--
Larry Gilbert (L2G)
Oh wait, here we go...
http://www.python.org/ftp/python/doc/2.7.1/
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
o stop doing that, I can't think
of a good solution other that to host a snapshot of the docs
elsewhere.
--
Larry Gilbert (L2G)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
Great. Sounds like you've already defined a Portfile, then. If so, just
submit it to Trac. See the guide:
http://guide.macports.org/#project.contributing
http://guide.macports.org/#project.tickets
-- Larry Gilbert (L2G)
___
macports-dev mailing li
nual, MacPorts can put together installable packages,
too; so you might even be able to use it to build your DMGs. (I have not yet
been bold enough to experiment with this feature.)
-- Larry Gilbert (L2G)
___
macports-dev mailing list
macport
On Sat, Jan 29, 2011 at 12:10 PM, Ryan Schmidt wrote:
> Feel free to commit all these ports at once in a single revision, since
> they're clearly related.
In this case, I think I like that solution best of all. :-) Thanks.
-L2G
___
macports-dev mailin
s keyword expansion. Right now the best thing I can think of is using a
tool like Quilt to build up a series of patches, then doing some shell magic
to commit them all to Subversion one at a time.
--Larry Gilbert (L2G)
___
macports-dev mailing list
mac
On Jan 28, 2011, at 11:01 PM, Ryan Schmidt wrote:
> I seem to recall that the developers of git feel that keyword expansion in
source files is the work of the devil, and do not support it. Meanwhile,
Subversion does support it, and we use it in our files.
On Sat, Jan 29, 2011 at 10:46 AM, Blair
Is the use of Git for committing changes to Subversion approved, and if so,
are there any guidelines or tips for doing so?
I have prior experience using Git to work with a different Subversion
repository, so I know the general method. I just want to know about
the idiosyncrasies here (if they exis
I got 'em.
-L2G
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
38 (p5-app-rad)
http://trac.macports.org/ticket/24748 (p5-mac-growl)
Thanks
--Larry Gilbert
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
33 matches
Mail list logo
