Nautilus 2.5.3

[Franz Klammer]

Joe Marcus Clarke wrote:

>On Wed, 2003-12-10 at 15:07, Franz Klammer wrote:
>  
>
>>Joe Marcus Clarke wrote:
>>
>>    
>>
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>>I would advise anyone that's submitting a bug in either GNOME 2.5 or Evo
>>>>>1.5 to make sure all their libraries are in sync first.  That is, make
>>>>>sure each binary only links against one version of a given library. 
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>i'm doing nothing else as be sure that the libraries are in sync since 
>>>>i've installed
>>>>gnome 2.5 - they bring out updates in minutes ;-)
>>>>(the last libbonobo*-update completely shoots my gnome-installation.)
>>>>currently i'm thinking about an automated script that does the job in 
>>>>the background.
>>>>but that's not so easy:
>>>>a portupgrade -rf <port-name> updates every package in +REQUIRED_BY even
>>>>it's not necessary -  is there an easy way to figure out the _exact_ 
>>>>names of the ports
>>>>they _really_ using the given port?
>>>>   
>>>>
>>>>        
>>>>
>>>What do you mean?
>>>
>>> 
>>>
>>>      
>>>
>>olala! how i should describe it ... :-\
>>
>>maybe i'm completely wrong but:
>>i mean that i dont't believe that every port listed in 
>>/var/db/pkg/<PORT>/+REQUIRED_BY
>>must be rebuild to get everything in sync if <PORT> installes a newer 
>>version of a library .
>>
>>it would be easier and faster to sync if i didn't must do a
>>portupgrade -rf <PORT> (or -rf pkgconfig). instead only update also the
>>ports they really need the update to snyc everything.
>>    
>>
>
>When you're talking about something like glib, you need to upgrade all
>the ports in REQUIRED_BY.  If you really wanted to be clever with it,
>though, you could use ldd to see if a certain binary in a certain port
>is linked to a certain library.  If it is, then add that port to the
>upgrade list.
>
>  
>

i guess that means no. ;-)
maybe i should change my update frequency from many to a maximum one time
at day and do it in the following steps:

1. get the list of newer ports
2. update theses ports
3. merge the content of the files in REQUIRED_BY of all updatet ports
4. rebuild the ports in the list.

maybe also with a no-auto-update list with not so important/often needed 
ports.
this ports will be listet on a should-be-updated.log

if i have enough time i will look at this next week and if it useable i 
send it
to the list.

franz.

>Joe
>
>  
>
>>if i'm wrong: excuse the noise!
>>
>>    
>>
>>>Joe
>>>
>>> 
>>>
>>>      
>>>
>>>>i know that this could be dangerous - but i think not so dangerous as 
>>>>the last
>>>>bonobo-update ;-)
>>>>
>>>>franz.
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>Also try to include as much console/error output as possible (if it's
>>>>>relevant).  Sometimes, you may have to start bonobo-activation-server,
>>>>>for example, by hand to get all the necessary output.  And, of course,
>>>>>be sure to build all components with "-O -g -pipe" and STRIP= to ensure
>>>>>we get good stack traces.  Also, anytime you can provide a patch, please
>>>>>do so (even if it's a simple header file include patch).  The more
>>>>>patches we can feed back to GNOME, the more seriously they will take
>>>>>us.  Thanks.
>>>>>
>>>>>Joe
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>

-- 
webonaut.com :: web technology
klammer at webonaut.com :: http://webonaut.com/
fon +43-664-3434708
--
MIG_media intelligence group > agentur für werbung & neue medien
A-5020 Salzburg > Linzergasse 21

Fon +43-662-453091-0 > Fax -99
office at mig.co.at > http://www.mig.co.at
--