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
So far, The description.txt file is note edited automatically by the plugins. And the user has to manage dépendencies.
It is true that it could be very convenient to automatically manage, when it is possible this field of the the description file.
But this has to be studied, in order to keep the package consistent.
The main piffal stand and the possibility to mix 2 editing way of the package.
A package can be edited without the GUI, and in this case the depnedencies has to me managed by the editor.
When a package is edited by plugins, we could manage to add the dependency if necessary, but managing to remove a dependency is not so simple.
In the gvle menu 'Packages > Current packages dependencies', it is possible to check and to uncheck the packages that are dependencies of the current package.
Almost, i did'nt remember this.
But my idea was more about a complete automation system.
I mean when we add a discrete time class inside a package, of course we do a add a dependency.
But i'm not sure of the feasibility of a total automation?
The dependance to discrete-time isn't added in the file "Description.txt" of the package. I have to add it manually.
The text was updated successfully, but these errors were encountered: