On 2012/05/07 15:09, Rainer Müller wrote:
> On 2012-05-07 21:07 , Mark Perkins wrote:
>> So now my question is "why"? Even though my tree is newer than what is
>> installed, shouldn't I be able to see things relevant to my installation?
One small clarification. Everything about dbus appears to
On 2012-05-07 21:07 , Mark Perkins wrote:
> So now my question is "why"? Even though my tree is newer than what is
> installed, shouldn't I be able to see things relevant to my installation?
The 'port notes' command is always evaluating the current Portfile in
the ports tree. There is no way to
On Mon, May 7, 2012 at 2:07 PM, Mark Perkins wrote:
>
> So now my question is "why"? Even though my tree is newer than what is
> installed, shouldn't I be able to see things relevant to my installation?
>
Those are the kind of insights only available from an oracular source
(trans. "I think Rya
I ran it both ways. Same result, as I would expect. But I think I found
the source of the problem, though I don't understand it
* I have dbus @1.4.18_0 is installed
* I recently did a 'port sync', so the port tree has
-> port info dbus
dbus @1.4.20 (devel)
* On an
Running "port notes dbus" gives me this:
dbus has the following notes:
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following comman
Greetings,
Messages/notes often fly by unnoticed when printed during installation,
especially for ports that are built as dependencies of others. The note
about startupitem for dbus is a topical example. 8-)
How do I (re)view any such messages? I *thought* that
port notes
would do the