Date: Wed, 26 Aug 2020 07:44:52 +1000 From: Dewayne Geraghty <dewayne@heuristicsystems.com.au> To: figosdev <figosdev@protonmail.com> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: What are my options regarding deprecated PyPy port? Message-ID: <42d673a6-8b84-af95-832f-359471a75944@heuristicsystems.com.au> In-Reply-To: <Vs7h5zc6vnKiYVCiqTbwEn7yrC7x8VQfIZyYVuO_jY8bbN9Rqhc9RCX14dWqeOoBBEuyaaH6EYl01xd3lUGJYYl8XNEsOXsKh6Zsi-YG-fc=@protonmail.com> References: <SQAZKeXAUxiRGkyHyx86icqCtJIj5DiJXW_wNgamtZLSVUI3YxMXR_6S-AGzvBJQP5J8WN2wmTTiSLOeXxy9mRcopivJ5omwokBnF_9FZXI=@protonmail.com> <470fc9d4-40e7-be12-f904-31f305f77813@heuristicsystems.com.au> <Vs7h5zc6vnKiYVCiqTbwEn7yrC7x8VQfIZyYVuO_jY8bbN9Rqhc9RCX14dWqeOoBBEuyaaH6EYl01xd3lUGJYYl8XNEsOXsKh6Zsi-YG-fc=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/08/2020 7:12 am, figosdev via freebsd-ports wrote:
>> the easiest way, if you build your own ports, is to svnlite update -r '{2020-03-29}' /usr/ports/security/w3af Note the date before removal from the ports tree.
>
> Thanks, this is probably what I was looking for (a way to get a copy of the existing work if ports deletes it).
>
You're welcome :)
> Forgive my lack of experience here-- does this imply that when something is "deleted" from ports-- it is like an edit in git or Wikipedia, where the old version still (typically) exists in the tree somewhere? Because if a year from now I can still get the old ports code from the older tree, that's good enough for me.
>
I can't speak to git or wikipedia, but I use this technique for ports
that go back to 2018-12-14. So you should be ok for awhile, perhap a
ports infrastructure person can illuminate. Though frankly, I keep
copies of all local tree changes against a pristine copy of the ports
tree ("diff -urN" is useful)
You should be aware that the mailing list(s) has mentioned a move to
git, and there is an intention to retain the svn feed, so we should be
fine for the foreseeable. Also mentioned was a transition guide...
> I also got the downloadable Linux ELF pre-compiled version from pypy.org to run in Linuxulator-- this has me covered for most of the stuff I do with Python, though for GUI stuff it doesn't seem to like the libc in /compat or the one I copied (a point for another list, but for me this solves most of my issue.)
>
A bit unfortunate that you need to, though its a resilient workaround :)
> Same GUI stuff runs on the native PyPy. I'm hoping the PyPy devs find a way to make this work, I intend to ask them if they can make a FreeBSD download again. They did one for FreeBSD64 a long time ago.
>
Yes, the best way is to try to get the upstream folks to modify their
code for python3. Though if the dev doesn't want to, you (we) need to
make a calculated risk determination, as I've found with a few very
useful applications (ports).
And as a general rule, I'd suggest avoiding unmaintained ports that
enable inbound network access.
Cheerio.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42d673a6-8b84-af95-832f-359471a75944>