Closed julien-duponchelle closed 8 years ago
Yep, I was thinking this. The is the main drawback of the current system is that we must always keep updating .gns3a
This would allow more flexibility but we have to do it correctly...
Yeah and suggesting people to send us the new settings.
On Tue, Feb 2, 2016 at 7:23 PM Jeremy Grossmann notifications@github.com wrote:
Yep, I was thinking this. The is the main drawback of the current system is that we must always keep updating .gns3a
This would allow more flexibility but we have to do it correctly...
— Reply to this email directly or view it on GitHub https://github.com/GNS3/gns3-gui/issues/980#issuecomment-178737209.
Maybe define URL templates instead of individual files? Like:
"version-constraint": "\\d+\\.\\d+(\\.\\d+)?(rc\\d+)?",
"image_templates": [
{
"filename": "chr-{version}.vmdk",
"url": "http://download2.mikrotik.com/routeros/{version}/chr-{version}.vmdk"
},
{
"filename": "chr-{version}.vdi",
"url": "http://download2.mikrotik.com/routeros/{version}/chr-{version}.vdi"
},
{
"filename": "chr-{version}.img",
"url": "http://download2.mikrotik.com/routeros/{version}/chr-{version}.img.zip",
"compression": "zip"
},
]
And search for any files that match that pattern, while also letting the user to import a file matching the pattern.
When automatic download comes into play, also allow the user to type arbitrary version that matches the pattern and display the size and MD5 of the downloaded file, asking the user to confirm or retry.
Andrew say that:
But it can be better to allow user to import not recognized image in case of the manufacturers release a new image.