Date: Thu, 13 Aug 2020 09:29:53 -0700 From: Chris <portmaster@BSDforge.com> To: <freebsd-ports@freebsd.org> Cc: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Subject: Re: pkg feature request Message-ID: <3dfd0e0311d4f3729922c098594353f4@udns.ultimatedns.net> In-Reply-To: <3269252.j5jfTYeP2b@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Aug 2020 10:17:34 +0100 Mike Clarke jmc-freebsd2@milibyte=2Eco=2Euk = said > On Wednesday, 12 August 2020 05:05:17 BST Tatsuki Makino wrote: >=20 > > But it seems to be a mixture of various revisions because poudriere is > > building it=2E > > svnlite up -q -r COMMITTED $PORTSDIR/category/name seems to be a > > revision of the package when it was built=2E >=20 > What would be needed would be for pkg to provide the revision number of t= he > ports tree used by=20 > poudriere at the time of the build, not the revision of each individual p= ort=2E > For example for 12=2E1- > RELEASE amd64 > http://beefy6=2Enyi=2Efreebsd=2Eorg/jail=2Ehtml?mastername=3D121amd64-default[1] = shows >=20 > that at the time of writing this email the latest completed build is 5443= 49 > and there is a build run in=20 > progress for 544776=2E If this revision number could be stored as a propert= y of > the repository then=20 > pkg could have a command (e=2Eg=2E 'pkg revno') which would currently return > 544349=2E After the=20 > current build has completed and propagated to the repository then 'pkg re= vno' > would return=20 > 544776 after the next time I run 'pkg update'=2E >=20 > I'm already using a manual version of this process=2E If today I needed to > build one of the few ports=20 > for which I don't use packages I would get the revision number of the lat= est > poudriere build and run=20 > 'svnlite up -q -r 544349 /usr/ports' to sync my ports tree with the versi= on > used for the repository=2E=20 > Providing I allow enough time for the new build to be transferred to the > FreeBSD repository before=20 > doing this it works fine=2E It would, of course, be much better if I could > obtain the revision number of=20 > the repository directly from pkg=2E >=20 > The real icing on the cake would be to have a command 'pkg sync-ports' wh= ich > would use the=20 > revision information to upgrade the ports tree in one go without needing = to > manually run svn=2E +1 Yes, please=2E Even if only the src rev the packages were built from=2E Cobblin= g up a script to capture the output of pkg srcrev/revno would be trivial to p= ass to svn up/co=2E :-) >=20 > --=20 > Mike Clarke >=20 > -------- > [1] http://beefy6=2Enyi=2Efreebsd=2Eorg/jail=2Ehtml?mastername=3D121amd64-default --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3dfd0e0311d4f3729922c098594353f4>