# mv composer.phar /usr/local/bin/composer
bash-5.0$ composer -V Composer version 2.0.7 2020-11-13 17:31:06 bash-5.0$
bash-5.0$ su Password: bash-5.0# composer self-update Upgrading to version 2.0.11 (stable channel). Use composer self-update --rollback to return to version 2.0.7
bash-5.0$ composer -V Composer version 2.0.11 2021-02-24 14:57:23 bash-5.0$
Tangential question: running slackware, do you have to install all the dependencies for packages by specifying them individually in conjunction with the command for installing a package?Since i'm on slackware normally i will install only software as a package(cleanly installs and can cleanly be removed) , using the appropriate slackbuild.
This is good information, succinctly stated. What more can a person hope to find? thank you! I feel safe following the path that is working for your slacker rig. Your mention of slackware led me my favorite search engine (Qwant), where I learned the concept behind slackware is to minimize changes to packages from upstream, and to generally minimize everything.However with composer i've never had a problem downloading and installing manually and it doesn't have any deps.
mmm probably should be another thread. For brevity will try to keep short. A slackbuild is a bash script that in essence is a more regulated and predictable way of using software source code; rather than:Tangential question: running slackware, do you have to install all the dependencies for packages by specifying them individually in conjunction with the command for installing a package?
Ok, this all makes sense. This explanation is just right for what I was looking for.mmm probably should be another thread. For brevity will try to keep short. A slackbuild is a bash script that in essence is a more regulated and predictable way of using software source code; rather than:
it evokes another executable at : /sbin/makepkg and creates a package that is manually installed; maybe similar to dpkg -i somedebfile.deb
For deps you have to read all the info at slackbuilds.org and use another slackbuild for each dep, build the pkg and manually install it. Its a bit prehistoric , but i like it since you have to read about each package and the deps.
Also there is slpkg which from the command line can search for packages and on evoking install, will also get the deps and install them, a bit like apt or apt-get. So there is package management & dep resolution in slackware if you so choose
Once again - Debian stable uses older packages to ensure that your system is as stable and bug-free as possible. Security updates are back-ported to these older releases. So it would be expected for the Debian package for composer to be slightly older.I am confused by these alternatives. Composer is available as a package that can be installed with APT.
It surprises me when I look at instructions for installing Composer on Debian 10, usually the Composer installer is recommended instead of the package through the apt repo.
Can you possibly explain what is going on with this?
self-update Updates composer.phar to the latest version.
bash-5.0$ composer check-platform-reqs Checking platform requirements for packages in the vendor dir ext-curl 7.4.1 success ext-intl 7.4.1 success ext-json 7.4.1 success ext-mbstring 7.4.1 success php 7.4.1 success bash-5.0$