Arca Noae Package Manager Fresh Install
I was just trying a fresh install of Arca Noae Package Manager on eComStation 2.1.
Installing it on a Fresh Environment
It is a rally fresh installation with the default software that cames into it, just installed as prerequistes:
- kLIBC Pathrewriters
I just rebooted just in case, you never know.
After that I installed the WarpIn Package of the Package Manager without any issues. It also installed some missing DLLs.
When I run the software for the first time it showed me that I don't have RPM or YUM installed, so it asked if I wanted let Arca Noae Package Manager to install that software for me.
So, I allow it and started to download the software.
It asked me on which drive to install RPM/YUM
It process something a little bit....
After installing it asked me to reboot.
After rebooting it is almost obvious... ok not "that obviuos"... that you are going to have some Libc/gcc libraries conflict, since ANPM will install some newer libraries on the FHS structure.
So checking "eComStation Kernel" on the "System Setup" you can find some of the conflicts.
It looks to me that you are you going to have duplicated DLL's and programs on:
Single Package install
Look for the package you want to install on "Available", right click and select install.
Check the package that is going to be installed.
What a little bit for it to download and install.
The package is now installed and it shows on "Installed".
Batch packages install (Quick Install)
I also tried to install a lot of packaged in one single shot:
zip unzip git openssl curl zlib stdcpp mmap pthread urpo gcc-stdc++-shared-library \ libc poppler libodin libqt libkai libjpeg libxslt libicu libxml2 aspell
Check out "Quick Install"
Put all the packages that you want to install at once.
Check the information and start installing.
More Information About the Packages
You can also view more information about the packages, even before downloading or installing them.
More information on the package can be display:
You can see more information about the package, license, etc.
You can also check the contents of the file.
It will show you the files that comes on that package.
It was also very interesting to see that ANPM also find the conflicts on the LIBPATH for the DLLs and gives you a warning: