Date: Fri, 13 Aug 2010 08:13:40 -0700 From: Chip Camden <sterling@camdensoftware.com> To: freebsd-questions@freebsd.org Subject: Re: Building and running new package versions not yet in ports? Message-ID: <20100813151340.GA29209@libertas.local.camdensoftware.com> In-Reply-To: <4C6502B8.8050600@infracaninophile.co.uk> References: <4c64e9c5.QP7fekph3VlfDjdr%mueller6724@bellsouth.net> <4C6502B8.8050600@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Matthew Seaman on Friday, 13 August 2010: > On 13/08/2010 07:44, Thomas Mueller wrote: > > What do I do if I want to build and run a package where version in > > ports collection is not up-to-date, and I want to build and run the > > current release version of that package, like Abiword 2.8.6 for > > instance, when version in ports is behind? Or maybe I want to try a new > > alpha or beta development release of a package like Firefox or > > Seamonkey, but don't want to burn my bridges on the already installed > > and running version. >=20 > Contact the port maintainers in the first instance -- they may well have > beta test versions of the ports you can download. Failing that, it is > perfectly feasible for you to update a port yourself. >=20 > Generally, you will want to work on a copy of the port directory > somewhere. You can check out what you need from anonymous CVS, which > gives you all the extra VCS goodness you could want for serious code > hacking. Your working directory doesn't have to be anywhere special in > relation to the ports tree. Anywhere you like will be fine. Well, > assuming the port you're working on is pretty much stand alone -- if you > need to look at a collection of highly interconnected ports then it gets > harder, but that's not something particularly common. >=20 > Refer to the Porter's Handbook for a guide on how it all should work, > and read the comments and code in /usr/ports/Mk/*.mk for the > nitty-gritty details. Ion-Mihail's guide at > http://ionut.tetcu.info/FreeBSD/How-to-submit-a-diff.txt has plenty of > good tips too. >=20 > If you do generate a usable upgrade for a port, please submit it as a PR > so the rest of the world can benefit. Beware though: thus begins the > slippery path to port maintainership and possibly even a coveted > @freebsd.org e-mail address. >=20 > > Can I create a testing install base such as /extra or /usr/extra, > > and set something like > > PATH=3D/usr/extra/bin:$PATH and perhaps modify some other environment > > variables, and then be able to return to the regular environment? I > > would only want to change a few things temporarily and would not want > > to create an entire chroot system. >=20 > Sure. When testing ports, I regularly have the following set in the > environment: >=20 > setenv WRKDIRPREFIX ${HOME}/tmp/ports > setenv PKG_DBDIR ${HOME}/tmp/db/pkgs > setenv PORT_DBDIR ${HOME}/tmp/db/ports > setenv PREFIX ${HOME}/tmp/local > setenv INSTALL_AS_USER yes > setenv NOCLEANDEPENDS yes > setenv PACKAGES ${HOME}/tmp/packages >=20 > > Is this the proper list for this question, or should I have posted > > to freebsd-ports@freebsd.org ? >=20 > You're more likely to find interested and knowledgeable people on > freebsd-ports@ -- certainly post there if you run into difficulties > trying to work with ports. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 That's some great information. Thanks, Matthew. --=20 Sterling (Chip) Camden | sterling@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com | http://chipsquips= .com --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iQEcBAEBAgAGBQJMZWEkAAoJEIpckszW26+R6GIIAMpn3CIb0rt96ZPghPXM7T+K KWctw4nWciCrzWjTRSfbC5/BXwyUpos+uNM3apohN3J8P+2toOD4OeRzwNpD1dTY pejPQ4a6SnGoiu7rO6WMlEB7RYNQGBk4GWNRNJcSmuoR+0J6ueCYxynIOXpNnWCV xoUecpZA856nSFiyrJ7brKqsj61I9ueAAwnMea4JL1tZePEx8qscDcko/uIPcWFr Z3rVMjDbwtCgbOnRrn1xKyzI+iD6Y8EbOcurgWHDVI2acK3VNuknv+kKLsTJDVDG TU5AuhEz5m0XhIBcj3u5lMZR+CDtu4CZlkWpNKamQ4b+n5p73K2XHV8zjfpJfcU= =gZGc -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100813151340.GA29209>