Thank you for the solution!
I have created a new release with the changes you propose.
Source package: http://birdfont.org/releases/birdfont-0.18.tar.gz
Portfile: http://birdfont.org/Portfile
Binary package:
http://sourceforge.net/projects/birdfont/files/Birdfont/birdfont-0.18.mpkg.zip/download
On Tue, Feb 26, 2013 at 04:23:12PM +0100, Johan Mattsson wrote:
I have created a new release with the changes you propose.
Glad you found a solution!
Source package: http://birdfont.org/releases/birdfont-0.18.tar.gz
Portfile: http://birdfont.org/Portfile
Do you want us to include the
Do you want us to include the Portfile in the MacPorts tree?
Yes, that would be nice.
This binary package is built with /opt/local as prefix. This will cause
problems when somebody has MacPorts installed and also installs your
binary package. See
Thank you I will fix that when the rebuild of
On Feb 26, 2013, at 9:29 AM, Yu Chen che...@umbc.edu wrote:
I have just installed tkdiff, but upon launch, it quits with the following
error, wondering if anybody has any idea. The same tkdiff works fine on
10.7.5. Thanks for your help.
==
actual font: -family Monaco
On Feb 25, 2013, at 3:42 PM, Jan Stary wrote:
The modification IMHO belongs to port(1) itself:
remember what was installed in this run, then
print out all the messages (as opposed to printing
every message just after the given port is installed),
so that they are in one place and the user
NTFS-3G on Macports lists fuse4x as a dependency. Does that mean when building
NTFS-3G as an installer package, that it will install fuse4x?
Since fuse4x has been merged into OSXFUSE, when can Macports depending on
fuse4x be expected to depend on OSXFUSE instead? And in the meantime, is it
On Feb 26 10:12:57, pixi...@macports.org wrote:
On Feb 25, 2013, at 3:42 PM, Jan Stary wrote:
The modification IMHO belongs to port(1) itself:
remember what was installed in this run, then
print out all the messages (as opposed to printing
every message just after the given port is
If you reply to a message to this list on this list
(as opposed to off-list), please reply To: the list.
Increasingly often, I see people replying To: the original
poster, with Cc: to the list. Such a message does reach
the recipients, but
(1) it breaks the list functionality:
none of the
On Feb 26, 2013, at 3:41 PM, Jan Stary h...@stare.cz wrote:
If you reply to a message to this list on this list
(as opposed to off-list), please reply To: the list.
meh
This is people doing 'reply-all' since few graphical MUAs do 'List-Reply'
Increasingly often, I see people replying To: the
On Feb 26 15:44:12, jer...@lavergne.gotdns.org wrote:
There is nothing wrong with that;
apparently I need to re-read the port manpage.
However, this still requires an action of the user besides 'install';
I believe that the notes of the newly installed packages (if any)
should be
On Feb 26, 2013, at 11:02 AM, Chris Murphy wrote:
NTFS-3G on Macports lists fuse4x as a dependency. Does that mean when
building NTFS-3G as an installer package, that it will install fuse4x?
Since fuse4x has been merged into OSXFUSE, when can Macports depending on
fuse4x be expected to
On Tue, Feb 26, 2013 at 09:41:18PM +0100, Jan Stary wrote:
Increasingly often, I see people replying To: the original
poster, with Cc: to the list. Such a message does reach
the recipients, but
(1) it breaks the list functionality:
none of the List-* headers is present in the message.
On Feb 26, 2013, at 4:10 PM, Jan Stary h...@stare.cz wrote:
(3) as an extreme case, after 'port update outdated',
there is no 'port notes depof:outdated';
the only way to get to all the install messages
of everything that got installed or updated
in this 'port update outdated'
The suggested 'port notes' works for a given package;
for example, if I run 'port install package', I can run
'port note depof:package' after that and get all the notes,
in one place. But:
(1) this should happen automatically
as a part of the 'port install'.
Well, we shouldn't put the
On Feb 26 16:34:07, jer...@lavergne.gotdns.org wrote:
The suggested 'port notes' works for a given package;
for example, if I run 'port install package', I can run
'port note depof:package' after that and get all the notes,
in one place. But:
(1) this should happen automatically
On Feb 26 15:27:57, spooky1...@gmail.com wrote:
On Tue, Feb 26, 2013 at 09:41:18PM +0100, Jan Stary wrote:
Increasingly often, I see people replying To: the original
poster, with Cc: to the list. Such a message does reach
the recipients, but
(1) it breaks the list functionality:
Surely the install process does some maintenance at its exit
(read: catches signals), and can spit out those messages even
if it is exiting due to being interrupted (as opposed to
finishing without error).
If MacPorts is quitting because the user is closing the window mid-process or
the
On Feb 26 16:56:23, jer...@lavergne.gotdns.org wrote:
Surely the install process does some maintenance at its exit
(read: catches signals), and can spit out those messages even
if it is exiting due to being interrupted (as opposed to
finishing without error).
If MacPorts is quitting
On Feb 26 23:22:46, h...@stare.cz wrote:
On Feb 26 16:56:23, jer...@lavergne.gotdns.org wrote:
Surely the install process does some maintenance at its exit
(read: catches signals), and can spit out those messages even
if it is exiting due to being interrupted (as opposed to
finishing
And even if he wanted to kill the ongoing installation,
why would he close the window, as opposed to simply
killing the process in that (terminal) window?
There's a button there, the user can hit it.
To lose any possibility of looking at the output?
It was an accident! Tell me you've never
On Tue, Feb 26, 2013 at 06:05:13PM +0100, Johan Mattsson wrote:
Do you want us to include the Portfile in the MacPorts tree?
Yes, that would be nice.
OK, see r103473[1]. A couple of comments:
- you can use port lint --nitpick on your package. This will check for
common mistakes and
Hi,
A simple notes happened above message would be ideal.
Conversely, we'd be spewing twice as many messages
if the install isn't interrupted.
Why? If the messages were _only_ printed at the end?
Why move where we're printing them when a simple hey, scroll up will
suffice?
Not
On Feb 26 17:35:45, jer...@lavergne.gotdns.org wrote:
And even if he wanted to kill the ongoing installation,
why would he close the window, as opposed to simply
killing the process in that (terminal) window?
There's a button there, the user can hit it.
To lose any possibility of
On Tue, Feb 26, 2013 at 10:53:09PM +0100, Jan Stary wrote:
On Feb 26 15:27:57, spooky1...@gmail.com wrote:
On Tue, Feb 26, 2013 at 09:41:18PM +0100, Jan Stary wrote:
There is a better way (with procmail, at least) that I use, which
gets all list e-mail filtered to the mbox I set aside for
On Tue, Feb 26, 2013 at 3:04 PM, Jan Stary h...@stare.cz wrote:
I agree, in such situations we cannot do anything.
How does that make install messages interspersed
in various places in the install output better
than having them at one place?
Perhaps it is minor, but because if you are
At 11:56 PM +0100 2/26/13, Chris Jones wrote:
A simple notes happened above message would be ideal.
Conversely, we'd be spewing twice as many messages
if the install isn't interrupted.
Why? If the messages were _only_ printed at the end?
Why move where we're printing them when a
On Feb 26, 2013, at 14:41, Jan Stary wrote:
I see people replying To: the original
poster, with Cc: to the list.
Yes. That is what happens when you press the Reply-All button in Mail.app.
Seems fine to me. Carry on.
___
macports-users mailing
On Feb 26 15:37:45, sewebs...@gmail.com wrote:
On Tue, Feb 26, 2013 at 3:04 PM, Jan Stary h...@stare.cz wrote:
I agree, in such situations we cannot do anything.
How does that make install messages interspersed
in various places in the install output better
than having them at one place?
28 matches
Mail list logo
