Portsnap is convenient, but svn/git in more inline with other tools.
Maybe some sort of middle ground where portsnap is replaced (or
re-written) with a wrapper around the svn checkout/update (or git
clone/pull) process.
On 8/13/2020 3:30 AM, Tatsuki Makino wrote:
We need to be reminded of cs
We need to be reminded of csup once in a while :)
Will portsnap be rewritten in C? :)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd
On Mon, 10 Aug 2020, Robert Huff wrote:
There are many users who never create any patches, but simply use the
ports tree to install software.
Add my name to that list.
Mine too; this is a great way to drive "ordinary users" away from FreeBSD
and towards, gasp, Penguin/OS...
I took up Fr
On Mon, 10 Aug 2020 12:11:06 -0400 Robert Huff roberth...@rcn.com said
Michael Gmelin writes:
> There are many users who never create any patches, but simply use
> the ports tree to install software.
Add my name to that list.
(Used to use cvsup ... now subversion ... soon git ... wh
On 8/11/20 9:39 PM, Mike Clarke wrote:
On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote:
What I'd like to see is a simple way to update the ports tree to match
what was used to build the current packages in the repository.
Something I've felt in need of for a long time, and su
On Sunday, 9 August 2020 17:27:01 BST RW via freebsd-ports wrote:
> What I'd like to see is a simple way to update the ports tree to match
> what was used to build the current packages in the repository.
Something I've felt in need of for a long time, and suggested from time to time
in the past
On Fri, Aug 07, 2020 at 11:48:34AM -0400, Greg Veldman wrote:
> On Fri, Aug 07, 2020 at 03:43:38PM +0200, Michael Gmelin wrote:
> > The real question is: Will we design things in a way that we expect ports
> > tree users to always install git and its dependencies on their system or
> > not (long
On Mon, Aug 10, 2020 at 3:21 PM Steve Wills wrote:
> On 8/10/20 9:28 AM, Lars Engels wrote:
> > On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
> >
> > I'm probably fine with this and I think that all of the (now) supported
> > methods have pros and cons.
> > To leverage the UX flaws
Michael Gmelin writes:
> There are many users who never create any patches, but simply use
> the ports tree to install software.
Add my name to that list.
(Used to use cvsup ... now subversion ... soon git ... where will
the insanity end? :-) )
Res
> On 10. Aug 2020, at 16:22, Steve Wills wrote:
>
> Hi,
>
>> On 8/10/20 9:28 AM, Lars Engels wrote:
>> On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
>> I'm probably fine with this and I think that all of the (now) supported
>> methods have pros and cons.
>> To leverage the UX f
Hi,
On 8/10/20 9:28 AM, Lars Engels wrote:
On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
I'm probably fine with this and I think that all of the (now) supported
methods have pros and cons.
To leverage the UX flaws of git and svn(lite) compared to portsnap
having a wrapper script
On Tue, Aug 04, 2020 at 02:43:20PM -0400, 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 t
On Sun, 9 Aug 2020 16:43:28 +0100
Matthew Seaman wrote:
> On 09/08/2020 07:03, Stefan Ehmann wrote:
> > I usually run `pkg version` to see what packages have changed.
> >
> > Previously, that was a more or less instant operation, now it takes
> > over 100 seconds. The problem is that /usr/ports/I
On 09/08/2020 07:03, Stefan Ehmann wrote:
> I usually run `pkg version` to see what packages have changed.
>
> Previously, that was a more or less instant operation, now it takes over 100
> seconds. The problem is that /usr/ports/INDEX-12 is missing.
Yes. For historical reason, the order of prec
On Tuesday, August 4, 2020 8:43:20 PM CEST 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 de
On 05 Aug 2020, at 04:59, Hans Petter Selasky wrote:
> 2) Should portsnap be a wrapper for GIT/SVN whatever is used?
Yes, this seems like a very obvious thing to do as it will minimize disruption
for the most users.
Not everyone has any use for git our any need to learn git syntax. A "portsnap"
By the way, there was a REFUSE directive in /etc/portsnap.conf, wasn't
there?
Isn't this a db space saver?
Or, rename the current fetch command to fetch-all.
Then the fetch command will be modified to download only where it is
needed based on the dependency graph.
portsnap fetch # <- download Mk/
On Fri, Aug 07, 2020 at 03:43:38PM +0200, Michael Gmelin wrote:
> The real question is: Will we design things in a way that we expect ports
> tree users to always install git and its dependencies on their system or not
> (long term)?
>
> For developers it???s a no-brainer (obviously yes), but po
> On 7. Aug 2020, at 15:26, Steve Wills wrote:
>
> Hi,
> .
> I believe that's updated daily and the tars from cgit are generated at least
> that frequently, if not more.
>
The real question is: Will we design things in a way that we expect ports tree
users to always install git and its
Hi,
On 8/7/20 6:19 AM, Michael Gmelin wrote:
On Fri, 7 Aug 2020 01:24:00 -0400
Steve Wills wrote:
Hi,
[snip]
2. Use svnlite to checkout a ports tree. (There will be git -> svn
replication.
Will this be a long-term option?
I don't know yet exactly how long the git to svn migration i
On 8/7/20 6:05 PM, Eugene Grosbein wrote:
> 07.08.2020 18:10, Ashish SHUKLA wrote:
>
>> Is there a similar seed file for subversion snapshot, that one can
>> download, extract, and "svn up" ?
>>
>> I was trying to "svn co" the ports tree, and it keeps dying in the
>> middle of checkout every few m
07.08.2020 18:10, Ashish SHUKLA wrote:
> Is there a similar seed file for subversion snapshot, that one can
> download, extract, and "svn up" ?
>
> I was trying to "svn co" the ports tree, and it keeps dying in the
> middle of checkout every few minutes.
ftp://ftp.freebsd.org/pub/FreeBSD/develop
On 8/6/20 6:05 PM, Mathieu Arnold wrote:
> On Thu, Aug 06, 2020 at 02:11:10PM +0200, Michael Gmelin wrote:
>>
>>
>>> On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
>>>
>>> On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> We welcome any constructive feedback. All input would
On Fri, 7 Aug 2020 01:24:00 -0400
Steve Wills wrote:
> Hi,
>
> On 8/5/20 6:17 PM, Michael Gmelin wrote:
> >
> >
> > What will be the process to bootstrap git?
> >
>
> There are several options:
Thanks for your response - ideally there would be a lean default way
users can rely on (henc
Hi,
On 8/5/20 6:17 PM, Michael Gmelin wrote:
What will be the process to bootstrap git?
There are several options:
1. Install the git package provided by the FreeBSD project
2. Use svnlite to checkout a ports tree. (There will be git -> svn
replication.
3. Download a tar of the ports tre
Mathieu Arnold wrote on 2020/08/06 20:57:
> `svnlite cleanup --remove-unversioned`
I have gained new knowledge.
I had erased the files ? marked with the following svnlite status with
my own hands :)
# svnlite status "`cat /usr/local/etc/poudriere.d/ports/svn/mnt`"
? /usr/local/poudri
On 2020-08-04 20:43, Steve Wills wrote:
> We welcome any constructive feedback. All input would be heard, and if the
> plans need to be amended, we will come back to you with the amended plan in a
> couple of weeks. This process will take some time and hopefully won't be too
> disruptive to any
On Thu, Aug 06, 2020 at 02:11:10PM +0200, Michael Gmelin wrote:
>
>
> > On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
> >
> > On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> >>> We welcome any constructive feedback. All input would be heard, and if
> >>> the plans need to
> On 6. Aug 2020, at 13:58, Mathieu Arnold wrote:
>
> On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
>>> We welcome any constructive feedback. All input would be heard, and if the
>>> plans need to be amended, we will come back to you with the amended plan in
>>> a couple of
On Thu, Aug 06, 2020 at 12:17:37AM +0200, Michael Gmelin wrote:
> > We welcome any constructive feedback. All input would be heard, and if the
> > plans need to be amended, we will come back to you with the amended plan in
> > a couple of weeks. This process will take some time and hopefully won'
On Thu, Aug 06, 2020 at 01:57:41PM +0700, Eugene Grosbein wrote:
> 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"
> >
> On 5 August 2020, at 23:57, Eugene Grosbein wrote:
>
> 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
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
> 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 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
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
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
> 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
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
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 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, an
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
-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: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
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
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 vers
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
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
Hi!
> > > > * This migration away from portsnap fits well with the planned
> > > > migration to git.
> > Have a look at the archive, and yes, subversion as version control
> > system for the FreeBSD project will probably be replaced by git.
> This is very bad news for us. I can make so many argu
On Wed, 5 Aug 2020 06:40:39 +0200 Kurt Jaeger p...@freebsd.org said
Hi!
> > * This migration away from portsnap fits well with the planned
> > migration to git.
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is on the horizon.
There's a list
Hi!
> > * This migration away from portsnap fits well with the planned
> > migration to git.
> Please tell me that this doesn't mean a
>
> [HEADS UP] Planned deprecation of subversion
>
> is on the horizon.
There's a list where the git topic is discussed:
https://lists.freebsd.org/pipermail/f
On Tue, 4 Aug 2020 14:43:20 -0400 Steve Wills swi...@freebsd.org said
We are planning to deprecate use of portsnap in ports.
...
Makes sense to me. Thank you. :-)
* Portsnap doesn't seem to save disk space compared to svn or git, if
you count the metadata (stored in /var/db/portsnap by defa
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't seem to save disk
53 matches
Mail list logo
