I completely agree with the original poster. Anjuta2 should have never replaced anjuta, as they are 2 different projects, with 2 different codebases, and anjuta2 is an alpha/beta release, that LACKS BASIC FUNCTIONALITY.
The fact that you can't use previous projects alone is enough to render it unusable for people like me, that have a > 340 sourcefiles project that were perfectly ordered and set up for anjuta1. Now I can't use that project file, and I can't create a new project with the same functionality. Currently, anjuta package is unusable for a lot of people. I suggest separating anjuta1 / anjuta2 packages to provide the user with options as to which project he wants to use, if anjuta2 is to exist beyond experimental. I know we use unstable, but having non-properly-functional packages is way beyond the unstable release scope. Meanwhile, I'm compiling 1.2.4a from sources... until anjuta2 works properly or there's a debian anjuta1 package.
signature.asc
Description: This is a digitally signed message part
