Hi,
Thanks for the advise, although I have to make myself clearer. I was already able to fix the problem prior to posting the first message. What I meant about asking a CVS guru on my last post, if there is better fix than our current fix.
As of now we have acs-workflow back into acs-core. But logically when a user checkouts acs-core say on 4.7 or beyond he/she should not get acs-workflow anymore. Its a minor thing, but maybe some people out there have an alternative solution.
A real drastic solution but illogical is to really create a repository for acs-core. Packages will also have their own repository. Right now we have a single tree for the core and packages right?
Anyway the current situation is fine and good, but if some knows a better solution please post. Thanks.
