On 16 Sep 2014, at 07:44, Mojca Miklavec mo...@macports.org wrote:
On Tue, Sep 16, 2014 at 7:30 AM, Clemens Lang wrote:
Hi,
- On 16 Sep, 2014, at 03:56, Lawrence Velázquez lar...@macports.org
wrote:
Is there some overwhelmingly good reason we still provide these, given that
2.7
On Tue, Sep 16, 2014 at 8:19 AM, Christoph Deil
deil.christ...@googlemail.com wrote:
On 16 Sep 2014, at 07:44, Mojca Miklavec mo...@macports.org wrote:
On Tue, Sep 16, 2014 at 7:30 AM, Clemens Lang wrote:
Hi,
- On 16 Sep, 2014, at 03:56, Lawrence Velázquez lar...@macports.org
wrote:
On 2014-09-16 10:44, Mojca Miklavec wrote:
(Once again it would be nice to automatically uninstall all the
py24-foo ports, but I don't know how to do that and I don't consider
it to be a showstopper if we don't find an elegant solution soon.)
As soon as they are removed from the PortIndex,
On 06/set/2014, at 17:06, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
Also seems that it needs wasysym from:
texlive-fonts-recommended
On Sep 6, 2014, at 11:02, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
I’ve found that doxygen tries to use texlive-fontutils during build, and
On Sep 15, 2014, at 7:56 PM, Lawrence Velázquez lar...@macports.org wrote:
I'm trying to adapt Ned Deily's patches for Yosemite[1] to the Python ports.
Adapting them to all the Python 3.x ports was tedious enough, but now I've
made it to Python 2.4 and 2.5. I feel like I'm slapping bandages
Frank Schima writes:
On Sep 15, 2014, at 7:56 PM, Lawrence Velázquez lar...@macports.org wrote:
I'm trying to adapt Ned Deily's patches for Yosemite[1] to the Python ports.
Adapting them to all the Python 3.x ports was tedious enough, but now I've
made it to Python 2.4 and 2.5. I feel
Hello everyone!
I managed to finally take a look and use pypi2port. I can’t help but notice two
things:
1) No Portfile. I think it would be nice to have portfiles for our
tools.
A basic porfile would be easy, but a more “pythonic” solution would
be
write a
On Sep 15, 2014, at 10:37 PM, Mojca Miklavec mo...@macports.org wrote:
On Mon, Sep 15, 2014 at 10:39 PM, Ryan Schmidt wrote:
On Sep 15, 2014, at 2:43 PM, Bradley Giesbrecht wrote:
Is a dot . a legal character in variant names?
Oh, you're right, we have been avoiding dots in variant
On Sep 16, 2014, at 1:37 AM, Mojca Miklavec mo...@macports.org wrote:
Personally I would be in favour of +mysql5.5, +mariadb10.0 (also in
favour of renaming the port to mysql-5.5), but then again we have a
zillion of ports using +gcc48, +python34, +clang34 etc. If there is no
reason not to
On Sep 16, 2014, at 1:30 AM, Clemens Lang c...@macports.org wrote:
If I were you, I'd set a timeout and if nobody argues that we should keep them
for a good reason, delete them once the timeout has passed. Probably ask
-users,
too.
I like this.
While we're at it, isn't 2.6 unsupported as
Lawrence Velázquez writes:
On Sep 16, 2014, at 1:30 AM, Clemens Lang c...@macports.org wrote:
If I were you, I'd set a timeout and if nobody argues that we should keep
them
for a good reason, delete them once the timeout has passed. Probably ask
-users,
too.
I like this.
While we're
On 2014-9-17 04:23 , Lawrence Velázquez wrote:
My problem with python24 and python25 (aside from having to maintain dead
software) is that they aren't framework installations, making them even more
of a pain to deal with. Note the 2.4/2.5-specific logic in python-1.0, for
example. python26
It's been proposed on this list that we should rename MySQL ports e.g. mysql51
- mysql-5.1; this would be to match the existing new ports mariadb-10.0 and
mariadb-10.1. Consistency is good, especially within a particular type of
software (e.g. MySQL in this case) but renaming MySQL ports is
Hi Guys,
I am new to the list. I have started working on a guile20 port (for guile v
2.0.11). I'd like to call it guile20 to be distinct from the current guile (v
1.8.8) port. There is a guile16, so I'd like to check out the patches to see
if/how it can be installed alongside the guile
On Sep 16, 2014, at 8:27 PM, Matt Wette wrote:
I am new to the list.
Welcome!
I have started working on a guile20 port (for guile v 2.0.11). I'd like to
call it guile20 to be distinct from the current guile (v 1.8.8) port. There
is a guile16, so I'd like to check out the patches to
In article 987e50bd-3eb4-4fe3-bf08-29c3f7916...@macports.org,
Lawrence Velazquez lar...@macports.org
wrote:
On Sep 16, 2014, at 1:30 AM, Clemens Lang
c...@macports.org wrote:
If I were you, I'd set a timeout and if nobody argues that we should keep
them
for a good reason, delete them
Discussion moved from macports-users. Previous thread:
https://lists.macosforge.org/pipermail/macports-users/2014-September/036386.html
On Sep 16, 2014, at 9:33 AM, Daniel J. Luke wrote:
On Sep 15, 2014, at 6:58 PM, Ryan Schmidt wrote:
On Sep 15, 2014, at 5:13 PM, Daniel J. Luke wrote:
I
On Sep 16, 2014, at 9:54 PM, michae...@macports.org wrote:
Revision
125409
Author
michae...@macports.org
Date
2014-09-16 19:54:15 -0700 (Tue, 16 Sep 2014)
Log Message
gr-mac: add patch to fix packet_to_pdu block functionality, and notes on how
to make use of this GNU Radio module
Please don't create new py24, py25, py31, and py32 subports from now on. I'd
like to phase out and remove python{26,27,31,32} in the near future.
vq
On Sep 16, 2014, at 11:34 PM, khindenb...@macports.org wrote:
Revision
125411
Author
khindenb...@macports.org
Date
2014-09-16 20:34:28
If you have both whitespace and functional changes to make to a port, please
commit the whitespace changes before the functional ones, if you can at all
help it. Whitespace changes render `svn blame` completely useless.
vq
On Sep 16, 2014, at 11:37 PM, khindenb...@macports.org wrote:
On Sep 17, 2014, at 12:19 AM, Lawrence Velázquez lar...@macports.org wrote:
Whitespace changes render `svn blame` completely useless.
And yes, I'm aware you can use a @REV, but that's annoying extra work that can
be easily obviated with thoughtful commit ordering.
vq
21 matches
Mail list logo
