Date: Fri, 25 Aug 2023 20:18:39 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Craig Leres <leres@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: How do I configure a port to get a specific sourceforge commit? Message-ID: <20230826031839.DD932387@slippy.cwsent.com> In-Reply-To: <56d5e798-9bb4-ca9a-5fbf-59a7b17a334b@freebsd.org> References: <56d5e798-9bb4-ca9a-5fbf-59a7b17a334b@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <56d5e798-9bb4-ca9a-5fbf-59a7b17a334b@freebsd.org>, Craig Leres writ es: > I'm trying to update graphics/netpbm to an actively maintained repo (PR > 262212). I'm told by some that this is the current best choice: > > https://sourceforge.net/projects/netpbm/ > > Unfortunately its idea of "release management" is less than ideal. > > Let's say I browse this commit log: > > https://sourceforge.net/p/netpbm/code/4616/log/?path=/advanced > > and decide that release 11.03.04/commit r4606 is interesting. I can > download it if I click on "Tree" for that commit and then "Download > Snapshot" it gives me this as the "direct link": > > > https://sourceforge.net/code-snapshots/svn/n/ne/netpbm/code/netpbm-code-r4606 > -advanced.zip > > This definitely works. But I don't find an existing port that uses > sourceforge with a specific commit and no combination of > "MASTERSITES=SF..." I've tried works. > > I have something that does work but it's a horrible hack, essentially: > > DISTVERSION= 11.03.04 > MASTER_SITES= > ${MASTER_SITE_SOURCEFORGE:S,/project/%SUBDIR%/,/code-snapshots/svn/n/ne/netpb > m/code/,} > DISTNAME= netpbm-code-r4606-advanced > USES= zip > > Is there a less hacky way to do this? > > Craig > I proxy my -devel ports (cde-devel and motif-devel) based on SF sources through my GH account, and the wpa_supplicant-devel/hostapd-devel on a git repo at w1.fi using that method as well. This allows me to use GH plumbing. I probably wouldn't suggest this for a non -devel port but if you're ever thinking of a netpbm-devel, this may be easier, allowing the use of the GH plumbing in ports. What I do is clone the remote repo and change the remote name from origin to upstream, setting the GH remote to origin and pushing to GH. To update I git fetch upstream, git rebase upstream/main, and finally git push origin. This too is a hack, probably just as hacky as your hack. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230826031839.DD932387>