search

jecisc / Bazard

0 stars 0 forks source link

Monticello have strange behavior if a package begin by the name of another package #232

Closed jecisc closed 5 years ago

jecisc commented 5 years ago

Migrated case from Manuscript.

Original case: https://pharo.fogbugz.com/f/cases/18712 Status: Work Needed Project: Monticello Original Author: CyrilFerlicot Date: 9 July 2016 5:57:07 pm

Description:

If you have a project with a package named: 'My-package' and a package named: 'My-package-components' then Monticello have some strange behaviors. For example it happen a lot that these packages are marked as dirty or as 'not up to date' when this is false.

jecisc commented 5 years ago

Reply: Author: Stephane Ducasse Date: 5 September 2016 6:13:19 am

Message:

Cyril Indeed this is an old limit of monticello. I thought that you faced another scenario. The use of XXX-Core and XXX is not good. I always have XXX-Core XXX-Componnents no sub matching between names. I'm not sure that we can change it now. I hope that we will be able to deal with it with Git. I will ask nicolas.

jecisc commented 5 years ago

Reply: Author: CyrilFerlicot Date: 16 February 2017 11:22:30 am

Message:

The correction of this issue might break too many things. It should not be corrected in the stabilization phase.