On Tue, 04 Aug 2020 19:03:08 -0700
Chris wrote:
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is on the horizon.
I'm afraid that git is fashionable now.
___
freebsd-ports@freebsd.org mailing list
https
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On Tue, Aug 04, 2020 at 09:51:23PM -0700, Chris wrote:
> This is very bad news for us. I can make so many arguments against
> dropping subversion. It's really not (needn't be) a matter of either/or.
In this sentence, who is "us"?
Also, can you elaborate?
--
Mathieu Arnold
signature.asc
Descrip
From: Kurt Jaeger
Subject: Re: [HEADS UP] Planned deprecation of portsnap
Date: Wed, 5 Aug 2020 06:40:39 +0200
> There's a list where the git topic is discussed:
>
> https://lists.freebsd.org/pipermail/freebsd-git/
>
> Have a look at the archive, and yes, subversion as version control
> system
On 2020-08-04 20:43, Steve Wills wrote:
We are planning to deprecate use of portsnap in ports.
The reasons are as follows (in no particular order):
* Portsnap doesn't support quarterly branches, even years after
quarterly branches were created and changed to the default for non-HEAD
packages
On Wed, Aug 05, 2020 at 12:59:18PM +0200, Hans Petter Selasky wrote:
> On 2020-08-04 20:43, Steve Wills wrote:
> >
> > We are planning to deprecate use of portsnap in ports.
> >
> > The reasons are as follows (in no particular order):
> >
> > * Portsnap doesn't support quarterly branches, even y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 5 Aug 2020 13:32:10 +0200
Mathieu Arnold wrote:
> On Wed, Aug 05, 2020 at 12:59:18PM +0200, Hans Petter Selasky wrote:
> > On 2020-08-04 20:43, Steve Wills wrote:
> > >
> > > We are planning to deprecate use of portsnap in ports.
> > >
On Wed, Aug 05, 2020 at 12:40:26PM +0100, Bob Eager wrote:
> On Wed, 5 Aug 2020 13:32:10 +0200
> Mathieu Arnold wrote:
>
> > On Wed, Aug 05, 2020 at 12:59:18PM +0200, Hans Petter Selasky wrote:
> > > On 2020-08-04 20:43, Steve Wills wrote:
> > > >
> > > > We are planning to deprecate use of po
Hi,
On 8/5/20 5:42 AM, Yasuhiro KIMURA wrote:
From: Kurt Jaeger
Subject: Re: [HEADS UP] Planned deprecation of portsnap
Date: Wed, 5 Aug 2020 06:40:39 +0200
There's a list where the git topic is discussed:
https://lists.freebsd.org/pipermail/freebsd-git/
Have a look at the archive, and yes,
Steve Wills wrote:
We are planning to deprecate use of portsnap in ports.
The reasons are as follows (in no particular order):
* Portsnap doesn't support quarterly branches, even years after
quarterly branches were created and changed to the default for non-HEAD
packages.
* Portsnap doesn'
Hi,
On 8/5/20 12:31 PM, Ernie Luzar wrote:
I seems this is a done deal as changes are already being done now. So
the real question is, when is the portsnap utility going to be removed
from the base system? Will it happen in 12.2 or 13.0?
Full removal may not happen before 13.0 but hopefully
> On 4. Aug 2020, at 20:43, Steve Wills wrote:
>
>
> We are planning to deprecate use of portsnap in ports.
>
> The reasons are as follows (in no particular order):
>
> * Portsnap doesn't support quarterly branches, even years after quarterly
> branches were created and changed to the defa
from Hans Petter Selasky:
> Maybe some silly questions already answered:
> 1) portsnap is populating /usr/ports . Is this location still hardcoded
> for ports tree installations, or can it be installed anywhere?
> 2) Should portsnap be a wrapper for GIT/SVN whatever is used?
> 3) Should /usr/p
Is there any command other than "rm -rf /usr/ports ; portsnap extract"
that can be easily repaired?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubsc
06.08.2020 6:02, Tatsuki Makino wrote
:
> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
> that can be easily repaired?
svnlite revert -R /usr/ports
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
>
> 06.08.2020 6:02, Tatsuki Makino wrote
> :
>> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
>> that can be easily repaired?
>
> svnlite revert -R /usr/ports
master# svnlite revert -R /usr/ports
svn: E155007: '/usr
06.08.2020 13:23, Doug Hardie wrote:
>> On 5 August 2020, at 21:30, Eugene Grosbein wrote:
>>
>> 06.08.2020 6:02, Tatsuki Makino wrote
>> :
>>> Is there any command other than "rm -rf /usr/ports ; portsnap extract"
>>> that can be easily repaired?
>>
>> svnlite revert -R /usr/ports
>
>
> master
17 matches
Mail list logo
