Recognise already installed packages (which might be tool-customised)

[dietmarw]

@casella pointed out some valid points on what if a to be installed Modelica package needs to be tweaked in order to work with the tool. In this case a stock-source library form the official repository will fail as it might lack certain compiled parts.

I propose to make impact aware to already installed Modelica packages in the target directory and to not overwrite them by default if the same or later (build) version is present. There should be a -f | --force switch available installing such Modelica packages anyway.

[xogeny]

This is inline with the idea of maintaining a package.json. To be npm like, we could have an init subcommand that looks for local packages and automatically adds them to package.json.

[casella]

seems that I really need to lear git, I even have a nick on GitHub ;)

    Francesco

P.S. Yesterday we had Norwegian salmon anyway. We enjoyed immensely :)

Il 14/03/2014 11:00, dietmarw ha scritto:

@casella https://github.com/casella pointed out some valid points on
what if a to be installed Modelica package needs to be tweaked in order
to work with the tool. In this case a stock-source library form the
official repository will fail as it might lack certain compiled parts.

I propose to make /impact/ aware to already installed Modelica packages
in the target directory and to not overwrite them by default if the same
or later (build) version is present. There should be a |-f | --force|
switch available installing such Modelica packages anyway.

—
Reply to this email directly or view it on GitHub
#60.

Francesco Casella - Ph.D.
Dipartimento di Elettronica, Informazione e Bioingegneria
Politecnico di Milano
Via Ponzio 34/5
I-20133 MILANO - ITALY

Tel: +39-02-2399-3465 (Leonardo)
+39-02-2399-7749 (Polo di Cremona)
Fax: +39-02-2399-3412
e-mail: francesco.casella@polimi.it
web: http://home.dei.polimi.it/casella
Skype: callto://francesco.casella

[xogeny]

It would be good if we could meet and discuss what this workflow would look like? I'm just not sure I have a good sense of the "big picture" here when it comes to version control related functionality on the install side.