Recently I have been collaborating on the *livecheck*
(https://github.com/Tatsh/livecheck) project that allows ebuilds to be
updated automatically, similar to the project *nvchecker*
(https://github.com/lilydjwg/nvchecker)
I see a very interesting utility to automate the process of updating an
This allows passing additional options to ssh.
Signed-off-by: Ulrich Müller
---
v2: Quote the options in the wrapper script
eclass/cvs.eclass | 12
1 file changed, 12 insertions(+)
diff --git a/eclass/cvs.eclass b/eclass/cvs.eclass
index 1289ee54cc3b..007240e6ba25 100644
--- a/ecl
> On Thu, 17 Oct 2024, Mike Gilbert wrote:
>>
>> -oUserKnownHostsFile="${known_hosts_file}" \\
>> -oForwardX11=no \\
>> -oClearAllForwardings=yes \\
>> +
On Thu, Oct 17, 2024 at 1:58 AM Ulrich Müller wrote:
>
> This allows passing additional options to ssh.
>
> Signed-off-by: Ulrich Müller
> ---
> eclass/cvs.eclass | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/eclass/cvs.eclass b/eclass/cvs.eclass
> index 1289ee54cc3b..5148daa2d
On Thu, 2024-10-17 at 08:47 -0400, Jérôme Carretero wrote:
> On Thu, 2024-10-17 at 14:12 +0200, Michał Górny wrote:
> > Hello,
> >
> > Given that you've expressed your preference for dev-lang/python
> > remaining slotted, I'd like to open another can of worms: should we
> > slot
> > PyPy consisten
On Thu, 2024-10-17 at 14:12 +0200, Michał Górny wrote:
> Hello,
>
> Given that you've expressed your preference for dev-lang/python
> remaining slotted, I'd like to open another can of worms: should we
> slot
> PyPy consistently with it? Some history and then my ideas below.
>
FWIW I'm all for
Hello,
Given that you've expressed your preference for dev-lang/python
remaining slotted, I'd like to open another can of worms: should we slot
PyPy consistently with it? Some history and then my ideas below.
PyPy versioning
===
PyPy has basically two versions:
sys.version_in
