Hi

1 - Here's some info on the version numbers: http://r-pkgs.had.co.nz/description.html#version. 2 integers separated by dots or dashes is the minimum length, but can be up to 4. There's also the

2. Yes, it doesn't have a queryable API, just uses static assets. It doesn't need to build any html though (thats just for humans): it builds out a static package list by concatenating the individual files within each package, and that could be done dynamically.

3. That's right. There is devtools::release() but it looks like that only works for cran, so I think there's no consensus about a generic upload method. OTOH, once built its just a zip file so crafting the R to send it off over http is not hard.

Re: ProGet Handling of PowerShell Gallery Versions

I am seeing similar to what's reported in the earlier thread.

I have an aggregate feed set up to aggregate our internal packages and PSGallery. Machines on our network cannot connect to PSGallery direct due to the firewall and are only allowed to retrieve via this one feed.

For example package AWSPowershell, in PSGallery it shows versions 4.1.15.0. In the proget web interface it shows 4.1.15.

This confuses Install-Module - how do I fix it?

Hi

1 - Here's some info on the version numbers: http://r-pkgs.had.co.nz/description.html#version. 2 integers separated by dots or dashes is the minimum length, but can be up to 4. There's also the

2. Yes, it doesn't have a queryable API, just uses static assets. It doesn't need to build any html though (thats just for humans): it builds out a static package list by concatenating the individual files within each package, and that could be done dynamically.

3. That's right. There is devtools::release() but it looks like that only works for cran, so I think there's no consensus about a generic upload method. OTOH, once built its just a zip file so crafting the R to send it off over http is not hard.

Hi,

Was just wondering if the PoC made any progress at all?

Thanks!