Date: Wed, 23 Mar 2022 17:33:47 -0600 (MDT) From: Dale Scott <dalescott@shaw.ca> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-questions <freebsd-questions@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: using pkgs vs using a cms Message-ID: <1037078559.19823383.1648078427475.JavaMail.zimbra@shaw.ca> In-Reply-To: <Yjuo5wcUhs2op3TO@cloud9.zyxst.net> References: <Yjuo5wcUhs2op3TO@cloud9.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> What's the advantage in updating a port over using its > own ecosystem? > > examples: www/nextcloud and www/drupal9 > I can't speak to Drupal, but I installed Nextcloud and WordPress using the distribution packages from their projects and let them update themselves. For me I was more concerned about the pkg database (and possibiliy dependencies as well) being out of date after the first self-update. Of the eight or so PHP web apps I'm hosting, 2 update themselves, 4 don't have pkgs at all, and the others were giving me PHP and MariaDb/MySQL dependency conflicts, so it was simpler to not use pkgs at all and install them from project release tar balls or zip archives. The only downside for me is having to keep track of PHP module dependencies myself (which isn't necessaraly a bad thing). Dale
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1037078559.19823383.1648078427475.JavaMail.zimbra>