On 2022/05/31 12:49, portno12 wrote:
> thanks for input all.
> should at least maintainer be dropped due to them being unresponsive if an update gets shared?
Usually we go for at least a couple of rounds of 'maintainer timeout'
commits before doing that. And best to CC ports@ on diffs if you are not
getting a reply from a maintainer - it's always possible that they are
not seeing your message due to mail server/spam filtering issues, and
that may give a heads-up
> ------- Original Message -------
> On Tuesday, May 31st, 2022 at 12:36 PM, Stuart Henderson <stu@spacehopper.org> wrote:
>
>
> > On 2022/05/31 12:33, Yifei Zhan wrote:
> >
> > > On 22/05/31 12:12PM, Stuart Henderson wrote:
> > >
> > > > Does the current version in ports work?
> > >
> > > The current version works fine, you can test it with
> > > $ torsocks curl ifconfig.me
> > > which should give you a Tor exit IP address. (You need to
> > > have tor running.)
> > >
> > > I prefer to keep it, as dirty as this solution of hijacking functions
> > > is, it works for many use cases. The last commit is in 2021, so I
> > > consider it's not abondoned.
> >
> >
> > Yes absolutely, if it works then keep it
> >
> > > There is a WIP diff to update it to the latest version on my local
> > > tree, but it's not ready yet (still need to figure out some libc
> > > magic, maybe tomorrow).
No comments:
Post a Comment