Skip to content
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.

Handle +build.x properly #51

Closed
dietmarw opened this issue Jan 27, 2014 · 2 comments
Closed

Handle +build.x properly #51

dietmarw opened this issue Jan 27, 2014 · 2 comments

Comments

@dietmarw
Copy link
Member

Currently the versions as seen by impact include the +build.x part not just for listing the available versions (which is fine) but also for installation.

The problems are:

  1. When a user does impact install Modelica#3.2.1 nothing is getting installed since impact expects the complete version number including the +build.x part.
  2. Dependencies in library only state the version number without any build.

Solution:
When a users does impact install Modelica#3.2.1 simply install the latest available build and the same also when a version number is given as dependency. Still keep the functionality to explicitly state a to be installed build number.

@dietmarw dietmarw modified the milestones: Release v1.0.0 (at Modelica Conference), Release v0.5.0 Feb 28, 2014
@dietmarw dietmarw added the bug label Mar 4, 2014
@xogeny
Copy link

xogeny commented Dec 10, 2014

I consider this part of the work to be done for #83.

@xogeny
Copy link

xogeny commented Apr 19, 2015

Duplicate of #83.

@xogeny xogeny closed this as completed Apr 19, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants