On Feb 26 22:01:36, ctrelea...@cogeco.ca wrote:
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
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
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
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 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
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
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 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 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?
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham spooky1...@gmail.com wrote:
There is nothing wrong with KDE, as long as you properly install the
On Feb 25 00:05:09, jer...@lavergne.gotdns.org wrote:
Crown was a lovely autocorrect for cron
Crown job sounds a bit nasty though.
___
macports-users mailing list
macports-users@lists.macosforge.org
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver the messages in another manner: eg, cause them to open
in TextEdit or a browser window.
That needs the capability to open a window.
No way.
There may be something I'm
The point is that, if you missed it the first
time, you don't know to go looking for the
information. Let alone where to find it in the
mass of dependencies that may have been
installed. Experienced users know to scroll back
through their Terminal history; new users, not so
much. In the
At 2:05 PM +0100 2/25/13, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham spooky1...@gmail.com wrote:
[...]
3) Deliver the
Another idea would be to pause by default on all important messages, maybe
with an CLI argument to suppress the pause for people who don't need it.
On Mon, Feb 25, 2013 at 2:57 PM, Craig Treleaven ctrelea...@cogeco.cawrote:
At 2:05 PM +0100 2/25/13, Jan Stary wrote:
On Feb 24 20:50:52,
On Feb 25, 2013, at 5:42 AM, Jim Graham wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver the messages in another manner: eg, cause them to open
in TextEdit or a browser window.
That needs the capability to open
On Mon, Feb 25, 2013 at 07:56:13AM -0800, Bradley Giesbrecht wrote:
On Feb 25, 2013, at 5:42 AM, Jim Graham wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver the messages in another manner: eg, cause them to
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver the messages in another manner: eg, cause them to open
in TextEdit or a browser window.
That needs the capability
On Feb 25 11:18:38, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 07:56:13AM -0800, Bradley Giesbrecht wrote:
On Feb 25, 2013, at 5:42 AM, Jim Graham wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3)
How's about you just display all the packages messages
after the port(1) job finishes, and the user, uh, I don't know,
reads them?
It would probably be sufficient to re-display notes after a
more-than-one-port-was-installed command.
you are trying to fsck it in the ear.
Come on, Jan. No
On Feb 25 08:57:09, ctrelea...@cogeco.ca wrote:
At 2:05 PM +0100 2/25/13, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham
Back way before I expected to be able to return. Strange.
On Mon, Feb 25, 2013 at 08:13:39PM +0100, Jan Stary wrote:
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver
On Mon, Feb 25, 2013 at 08:20:19PM +0100, Jan Stary wrote:
On Feb 25 08:57:09, ctrelea...@cogeco.ca wrote:
Um, OS X includes this graphical user interface thingy. We don't
have to ignore it _all_ the time!
Which clearly is a reason to _display_text_ with a GUI.
Right.
Hmmm, I wonder
Hello from a fellow OM and MacPorts dev!
On 25/feb/2013, at 23:12, Jim Graham spooky1...@gmail.com wrote:
Back way before I expected to be able to return. Strange.
On Mon, Feb 25, 2013 at 08:13:39PM +0100, Jan Stary wrote:
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25,
On 2013-02-25 23:12, Jim Graham wrote:
Yeah, you said that, and someone else asked about using it in a non-GUI
environment. Ok, but it doesn't HAVE to be a GUI version. Switching
it from using a text widget and scrollbars would mean changing a few
lines of code (e.g., instead of $w.t insert
On Mon, Feb 25, 2013 at 11:29:58PM +0100, Alja?? Srebrni?? wrote:
Hello from a fellow OM and MacPorts dev!
Just to be clear, I'm not a macports dev
On 25/feb/2013, at 23:12, Jim Graham spooky1...@gmail.com wrote:
Since we are OM, let's talk radio
Ok. :-)
Say you do 150WPM CW on your
On Feb 25 16:12:12, spooky1...@gmail.com wrote:
Back way before I expected to be able to return. Strange.
On Mon, Feb 25, 2013 at 08:13:39PM +0100, Jan Stary wrote:
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24
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 doesn't
have to watch for it or scan the output.
There are issues on all fronts: crown job updates, distributed installs, etc.
No one size fits all :-)
Craig Treleaven ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham
On 25/02/2013, at 12:54 PM, Jeremy Lavergne wrote:
There are issues on all fronts: crown job updates, distributed installs, etc.
No one size fits all :-)
Notes that flash by are one of my pet (only) gripes in Macports. May I
suggest:
4) Macports remembers, on a temp file, which ports in
Crown was a lovely autocorrect for cron
Ian Wadham iandw...@gmail.com wrote:
On 25/02/2013, at 12:54 PM, Jeremy Lavergne wrote:
There are issues on all fronts: crown job updates, distributed
installs, etc. No one size fits all :-)
Notes that flash by are one of my pet (only) gripes in
So the notes are available easily enough as we have demonstrated, and we could
repeat spewing them again after all installations. I would hesitate removing
them after each installation as a user could halt the install process.
As for how many packed will be installed, that should be available
39 matches
Mail list logo
