You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear all, I think we really have to make a decision about how to use of bazaar / gitaar. Both of them are great tools, but having both is a waste of resources and energy.
Personally I find that:
bazaar is great for its user interface and the epm system. But it lacks code control, user contribution, versioning, dependencies, and it looks sooooooo oldie.
gitaar is a developer tool, so it has code control, users can contribute, we have versioning, it is modern. But it cannot be used by the normal repository manager who likes to enable / disable plugins.
Having both of them on your repository means that every time that you upgrade your eprints base version you have to go back in time and remember what you installed with gitaar, and what came with bazaar. Without speaking of the fact that, in both cases, you keep polluting your root installation.
Can we discuss this and try to find a solution? Unfortunately it is a too difficult project for me alone otherwise I would have provided some code, other that complains and ideas :)
The text was updated successfully, but these errors were encountered:
Dear all, I think we really have to make a decision about how to use of bazaar / gitaar. Both of them are great tools, but having both is a waste of resources and energy.
Personally I find that:
Having both of them on your repository means that every time that you upgrade your eprints base version you have to go back in time and remember what you installed with gitaar, and what came with bazaar. Without speaking of the fact that, in both cases, you keep polluting your root installation.
Can we discuss this and try to find a solution? Unfortunately it is a too difficult project for me alone otherwise I would have provided some code, other that complains and ideas :)
The text was updated successfully, but these errors were encountered: