Changes between Initial Version and Version 1 of Ticket #257, comment 6


Ignore:
Timestamp:
Jul 10, 2017, 10:04:31 AM (7 years ago)
Author:
dmik
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #257, comment 6

    initial v1  
    11Okay, I see your point. But the thing is that an `update all` getting screwed is even worse than this ticket's issue. It should be addressed in the first place then. It's **not** up to the user to decide upon the order in which they install packages — this beats the whole purpose of a smart package manager. This definitely deserves a separate ticket, created #260 for that.
    22
    3 Regarding #259 and error-proneness. By that I mean that it's easy to forget to add the exact version number of a particular DLL to the spec file, especially if there are a many DLLs getting forward-incompatible updates and/or many packages getting dependent on these updates. Regarding this particular case, I'm afraid I have to add a specific version dependency manually this time as #259 is not yet there and as `update all` isn't always reliable. Just note that even with these manually fine-tuned dependencies we don't solve a generic problem described in #260.
     3Regarding #259 and error-proneness. By that I mean that it's easy to forget to add the exact version number of a particular DLL to the spec file, especially if there are a many DLLs getting forward-incompatible updates and/or many packages getting dependent on these updates. Regarding this particular case, I'm afraid I have to add a specific version dependency manually this time as #259 is not yet there and as `update all` isn't always reliable. Just keep in mind that even with these manually fine-tuned dependencies we don't solve a generic problem described in #260.