On Thu, Jan 7, 2010 at 8:51 PM, Danie Roux <lists+pharo@danieroux.com<lists%2Bpharo@danieroux.com>
wrote:
2010/1/7 Mariano Martinez Peck :
I think we should wrote somewhere how to submit an issue
I followed http://code.google.com/p/pharo/wiki/HowToContribute :-) I missed the step to set the status to "Fixed" though.
Thank you!!! I was looking for that link and I didn't find it.
it's name and the trick of the dirty packages...
"The trick of the dirty packages". Sounds like a crime novel. But seriously, what is this trick?
Sorry for the confusion, you did exactly the correct. The trick is the following (I think it is the same that is explained there...) When you have changed several packages, you have to create another package called SLICE-IssueXXX-DeCRIPTION and then, you have to put to that package, the packages that you modified, as "requierd". Then, when you commit the slice package, it also commits the requiered packages, and thus, all of them are loaded when someone else load that slice package in another image. The trick is that most of the times, all the requiered packages are those who you have modified. So, there is an option (right button in a package) which says "add dirty package as requiered". Dirty in this case means modified. That's all :) Thank you very much! Mariano
-- Danie Roux *shuffle* Adore Unix - http://danieroux.com
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project