Date: Sat, 13 Mar 2021 09:51:36 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Michael Gmelin <grembo@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Testing www/chromium before installing Message-ID: <20210313175136.GA72527@www.zefox.net> In-Reply-To: <20210313181106.4e789b51@bsd64.grem.de> References: <20210313154902.GA72341@www.zefox.net> <F0A8732B-9147-410D-A9EB-8AD283A94857@freebsd.org> <20210313165007.GB72341@www.zefox.net> <20210313181106.4e789b51@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 13, 2021 at 06:11:06PM +0100, Michael Gmelin wrote: > > > On Sat, 13 Mar 2021 08:50:07 -0800 > bob prohaska <fbsd@www.zefox.net> wrote: > > > Hi Michel, > > > > On Sat, Mar 13, 2021 at 05:01:16PM +0100, Michael Gmelin wrote: > > > What about ???make stage???? > > > > > Never heard of it, and can't find any obvious references. > > Is there a description somewhere? > > It's one of the seven main targets of building a port: > > - extract > - patch > - configure > - build > - stage > - install > - package > > It installs the port into STAGEDIR (by default work/stage). Install and > package copy files from STAGEDIR, so usually stage is run implicitly. > See /usr/ports/Mk/bsd.port.mk for details (documentation isn't great, > most of it is from when the big conversion to STAGEDIR happened a > couple of years ago). > > To give you a simple port as an example > > # cd /usr/ports/editors/joe > # make stage > ... > # find work/stage -type f -perm +111 > work/stage/usr/local/bin/joe > > Same should work with chromium (you might need to set LD_LIBRARY_PATH > in case chromium comes with its own libraries). > Thank you! Found the executable, and it suffers from the same problem as the old version: The controls drop-down menu (right of the URL bar) is non-persistent and can't be used. The new version does seem to run faster, which is a step forward. It's surprising that a simple find . -name stage didn't discover the directory, but did discover those for node, in the same subtree. The exact syntax you provided seems to be required. > Oh, alternatively you could of course simply make a backup of your > current chromium package: > > pkg create chromium > > Which you then can re-install in case the new version doesn't work as > expected: pkg add chromium-someversion.txz > The sources for the existing version of chromium are long overwritten, can a package be constructed from installed files? bob prohaska > Best, > Michael > > > > > Thanks for writing! > > > > bob prohaska > > > > > > > > > > > > > > > > > > > > > > > > On 13. Mar 2021, at 16:49, bob prohaska <fbsd@www.zefox.net> > > > > wrote: > > > > > > > > ???After a _very_ long time www/chromium finished compiling on a > > > > Pi3B+. I'd like to test it before installing, since I have a > > > > (mostly) working version in /usr/local/bin and don't want to > > > > overwrite it until I know the new version works at least as > > > > well as the old one. > > > > > > > > Poking around in the source tree didn't disclose any obvious > > > > executable, could somebody offer a hint at test methods, if any? > > > > > > > > Thanks for reading, > > > > > > > > bob prohaska > > > > > > > > _______________________________________________ > > > > freebsd-ports@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > > > To unsubscribe, send any mail to > > > > "freebsd-ports-unsubscribe@freebsd.org" > > > > > > > > > > -- > Michael Gmelin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210313175136.GA72527>