How can I delete the older version of an application before installing the newer released version?
In other words, is there a way to automatically remove "MSIXDemoInstaller_1.0.0.0_Test" file before installing "MSIXDemoInstaller_1.0.1.0_Test" file?
You don't have to do anything special for this, the OS will handle it automatically. Just increase the version when building your new version. When you install it on a machine with the old version the OS will automatically apply it as an upgrade.
Related
We are currently running version 4.0.3 and can't go to the latest as support for our database has been dropped (SQL Server 2012). I would like to get the latest version 4 release (4.2.0) - can anyone tell me if this is possible and if so, where can I find it?
Apparently the source code for all previous versions is in GitHub. Now the question becomes "Is there anywhere I can find the Windows executable version of Flyway 4.2.0?"...
You will probably have to build the executable from source using one of the releases on their Github. 4.2.0 is available here
The various binaries, as well as the source, for 4.2.0 can be downloaded from Maven Central.
Here is the 4.2.0 Windows zip.
I'm trying to use the legacy version of R to run a package on Mac.
On Windows there is a switch in the General tab. However, it is not found on Mac RStudio. I referred to this post: https://support.rstudio.com/hc/en-us/articles/200486138-Using-Different-Versions-of-R
And I do not quite understand the 3 options:
Run the installer from CRAN for the R version you want to be current
List item Use the RSwitch utility available at: http://r.research.att.com/
Update the R.framework/Versions/Current directory alias directly
using ln -s
Especially for RSwitch utility, how do I even open/use that?
Thanks!
This old question is again timely, with the move to R version 4.
There is an RSwitch.app available for MacOS 10.14+ that provides this functionality via a menu bar app. You can choose which of your R builds to use, integrating with the standard Mac GUI and with RStudio. (I've had trouble with the newest Mac GUI not working with R 3.6.3 but RStudio seems to work fine with both that and R 4.0.1 along with this RSwitch.app.) The help pages for Rswitch show what's going on underneath, if you prefer to work via a command line.
If you use a standard .pkg via GUI to install a newer version of R it will effectively forget the other versions. You can use the command
pkgutil --forget (path to package name)
with the .pkg to overcome that. (I've had trouble installing from a tarball instead; might just be my incompetence.) Installing an older version from a .pkg won't overwrite a newer version but in that case it might be safest to omit any attempt to instal older Tcl/Tk and Texinfo, selectable with the "Customize" button at the "Installation Type" stage of the installation. With security settings in MacOS you might have trouble opening some R .pkg files; the awkward workaround is to use Control/right/two-finger click on the file in the Finder, then select ‘Open With’ and ‘Installer’ from the menu that appears.
The version of RSwitch.app noted in the question is still available via a link from this page. This is evidently 32-bit as it is disabled on my Mac under OS 10.14.
Thought I'd give MRO a spin, to see if it speeds up my usage in general.
I can't find the installed R though. Not as a separate, not as an overwrite.
/usr/local/bin/R contains R version 3.4.0 (2017-04-21) -- "You Stupid Darkness", which is also the one used by RStudio.
/Library/Frameworks/R.framework/Versions/ also only contains 3.4.
The GUI "Microsoft R Open.app" has the description R 3.3.0 GUI 1.68 Mavericks build... but it also returns 3.4.
What am I missing?
You've identified a bug in the installer. Thanks!
Looks like we are not installing the MRO framework files because the package installer is detecting a newer version (CRAN 3.4). We will get this fixed in the next release.
In the meantime, you can work around this by renaming /Library/Frameworks/R.framework/Versions/3.4 to /Library/Frameworks/R.framework/Versions/0.3.4 and reinstalling MRO. Then go ahead and rename it back.
Please note, as a part of the install we update the symlinks to point to our version, so if you would prefer the default R installation to be CRAN 3.4 please do the install in the reverse order or manually update the symlink to Current in the Versions folder.
How do I install multiple versions of R on a Mac without overwriting the old version? Where are the appropriate places to install them?
The most appropriate place would be in the R.framework directory. I have versions dating back to R 2.7 on this machine. Installing of a new version from the binary installation package will not overwrite earlier versions. This is what dragging the symlink "Current Version" folder gives when I drag-drop it into the current console window:
/Library/Frameworks/R.framework/Versions/Current
It's actually a reference to:
/Library/Frameworks/R.framework/Versions/2.15
(This is where the binary installer from CRAN will put successive versions by default if you just click OK to all the dialog boxes during installation.)
I'm planning a new build system for our project running on Centos 5.4. I intend to use SCons. I noticed the latest stable SCons version is 2.0.1 while Centos 5.4 comes with 1.2.
I'm new to SCons so I'd like to understand more about the features/stability ratio between the versions.
Would you recommend installing and using the latest version or sticking to what comes from my OS repository?
Since 1.2 the changes have been bug fixes and documentation improvements. There haven't been any new features.
The 2.x version of SCons drops support for Python versions older than 2.4, updating some of the internal code to use newer idioms but without affecting any user visible APIs. That's the reason for the major version number change. If CentOS comes with a recent version of python then this won't affect you either way.
There have been a lot of fixes for newer versions of the various Microsoft compiler versions, but this won't affect a CentOS install.
The bug fixes since SCons 1.2.0 also solve problems in the Fortran, TeX and LaTeX builders. If you make use of Fortran or LaTeX then it would probably be worth upgrading. Otherwise I think you would be hard pushed to spot any day-to-day difference between 1.2.0 and 2.0.1.