Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo
Status: New
Owner: ----
Labels: Type-Bug Milestone-2.0 Target-Nautilus

New issue 6611 by [hidden email]: Removing a package in Monticello  
is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

My sequence :
-Create a package in Nautilus
-Create a package of the same name in Monticello
-Remove the package in Monticello
-- No change in Nautilus.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo
Updates:
        Status: WorkNeeded-Conclusion

Comment #1 on issue 6611 by [hidden email]: Removing a package in  
Monticello is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

?

I just do not understand what you are talking about

Could you be more precise please ?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo

Comment #2 on issue 6611 by [hidden email]: Removing a package in  
Monticello is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

I tried again in 20463:
-Create a package in Nautilus
-Create a package of the same name with the Monticello GUI
-Remove the package in the Monticello GUI
-- Nautilus still shows the package.

Shouldn't Nautilus and the Monticello GUI be in sync when dealing with  
packages ?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo

Comment #3 on issue 6611 by [hidden email]: Removing a package in  
Monticello is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

there is a difference between the monticello package and the normal  
packages. They are not directly related (which is indeed strange).

Bear in mind the differences of the 2 following operations:

- unload a monticello package should remove it from the system (aka. also  
removed from Nautilus)
- deleting the working copy of a monticello package should only remove it's  
versioned history, but not touch the classes in the system.

I agree that the UI is rather confusing. Years of training made me fully  
ignore this :/

So I assume this is an invalid bug report?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo

Comment #4 on issue 6611 by [hidden email]: Removing a package in  
Monticello is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

Ouch for the dual package concept :( I have a preference for a synchronized  
concept.

Yes, you can consider the bug invalid.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 6611 in pharo: Removing a package in Monticello is not seen by Nautilus

pharo
Updates:
        Status: Invalid

Comment #5 on issue 6611 by [hidden email]: Removing a package in  
Monticello is not seen by Nautilus
http://code.google.com/p/pharo/issues/detail?id=6611

ok, invalid then :)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker