Portsnap and new git ports tree

[Arthur Barlow]

Anyone know when portsnap will be able to work with the new ports tree on
github?

[Daniel Stevenson]

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree on
github?

No, portsnap does not support Git. I would recommend using net/gitup from ports
instead and altering the "ports" section in /usr/local/etc/gitup.conf to look
like this:
....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....

--
Daniel Stevenson

[Daniel Stevenson]

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree on
github?

No, portsnap does not support Git. I would recommend using net/gitup from ports
instead and altering the "ports" section in /usr/local/etc/gitup.conf to look
....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....

My bad, the "repository" line should read:
....
"repository" : "/ports.git",
....

Sorry for the confusion!

--
Daniel Stevenson

[Kent Kuriyama]

Is the line:

"host" : "github.com",

Still retained? When I execute:

gitup -v 2 ports

I don't see any output. Thanks.

Kent

Post by Daniel Stevenson

On Wednesday, April 7th, 2021 at 08:23, Arthur Barlow

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree

on

Post by Arthur Barlow
github?

No, portsnap does not support Git. I would recommend using net/gitup

from ports

instead and altering the "ports" section in /usr/local/etc/gitup.conf to

look

....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....

....
"repository" : "/ports.git",
....
Sorry for the confusion!
--
Daniel Stevenson
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "

[Daniel Stevenson]

No, it isn't. The block I sent you points gitup at the project's own Git server instead of at the GitHub mirror.

--
Daniel Stevenson

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

"host" : "github.com",
gitup -v 2 ports
I don't see any output. Thanks.
Kent
On Wed, Apr 7, 2021 at 4:32 AM
Daniel

Post by Daniel Stevenson

On Wednesday, April 7th, 2021 at 08:23, Arthur Barlow

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree
on
github?

No, portsnap does not support Git. I would recommend using net/gitup
from ports
instead and altering the "ports" section in /usr/local/etc/gitup.conf to
look
....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....

....
"repository" : "/ports.git",
....
Sorry for the confusion!
--
Daniel Stevenson
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "

https://lists.freebsd.org/mailman/listinfo/freebsd-questions

[d***@safeport.com]

Post by Daniel Stevenson

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree on
github?

No, portsnap does not support Git. I would recommend using net/gitup from ports
instead and altering the "ports" section in /usr/local/etc/gitup.conf to look
....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....

....
"repository" : "/ports.git",
....
Sorry for the confusion!

I assume EOL for portsnap is in the near future. Including this information
in the "Support Lifecycle" "How to update your system" section would be
nice. This does assume that the ports tree is considered part of the base
system.

[Graham Perrin]

… I assume EOL for portsnap is in the near future. …

I should not expect deprecation until some time after the final RELEASE
of 12.⋯ reaches end of life.

<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>>
as a reminder that "… 11.x and 12.x will have it of course, …".

(I have seen some confusion from premature declarations that portsnap
_is_ deprecated.)

HTH

[Michael Sierchio]

Post by Graham Perrin

… I assume EOL for portsnap is in the near future. …

I should not expect deprecation until some time after the final RELEASE
of 12.⋯ reaches end of life.
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>>
as a reminder that "… 11.x and 12.x will have it of course, …".
(I have seen some confusion from premature declarations that portsnap
_is_ deprecated.)

in case I'm missing something, or in case this isn't obvious, Deprecated
does not mean EOL. Deprecated is a declaration that usage is discouraged,
and that support will be withdrawn in the future. In which case, use
portsnap is deprecated.

[Graham Perrin]

Post by Graham Perrin

… I assume EOL for portsnap is in the near future. …

I should not expect deprecation until some time after the final RELEASE
of 12.⋯ reaches end of life.
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>>>
as a reminder that "… 11.x and 12.x will have it of course, …".
(I have seen some confusion from premature declarations that portsnap
_is_ deprecated.)
in case I'm missing something, or in case this isn't obvious,
Deprecated does not mean EOL.  Deprecated is a declaration that usage
is discouraged, and that support will be withdrawn in the future.  In
which case, use portsnap is deprecated.

Yes and no.

Re: the presence and planned/prospective removal of portsnap, please see
(for example)
<https://forums.FreeBSD.org/threads/ports-transitioned-to-git.79598/post-504229>.

Re: use of portsnap,
<https://forums.FreeBSD.org/threads/ports-transitioned-to-git.79598/post-504232>.

[LuMiWa via freebsd-questions]

On Fri, 9 Apr 2021 03:42:48 +0100

Post by Graham Perrin

On Wed, Apr 7, 2021 at 9:22 AM Graham Perrin

… I assume EOL for portsnap is in the near future. …

I should not expect deprecation until some time after the final RELEASE
of 12.⋯ reaches end of life.
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html
<https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119114.html>>>
as a reminder that "… 11.x and 12.x will have it of course, …".
(I have seen some confusion from premature declarations that
portsnap _is_ deprecated.)
in case I'm missing something, or in case this isn't obvious,
Deprecated does not mean EOL.  Deprecated is a declaration that
usage is discouraged, and that support will be withdrawn in the
future.  In which case, use portsnap is deprecated.

Yes and no.
Re: the presence and planned/prospective removal of portsnap, please
see (for example)
<https://forums.FreeBSD.org/threads/ports-transitioned-to-git.79598/post-504229>.
Re: use of portsnap,
<https://forums.FreeBSD.org/threads/ports-transitioned-to-git.79598/post-504232>.
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to

I decided for retirement of portsnap and choose gitup. I didn't change
gitup.conf and just rename my old portsnap /usr/ports made new
/usr/ports, run gitup ports and it works than portmaster -ad and
everything is updated.

[The Doctor via freebsd-questions]

Post by Daniel Stevenson

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree on
github?

No, portsnap does not support Git. I would recommend using net/gitup from ports
instead and altering the "ports" section in /usr/local/etc/gitup.conf to look
....
"ports" : {
"repository" : "ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},
....
--
Daniel Stevenson
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions

Yes it is working, however try for a gitup.conf file


# $FreeBSD$
#
# Default configuration options for gitup.conf.
{
"defaults" : {
"host" : "git.freebsd.org",
"port" : 443,
"verbosity" : 1,
"work_directory" : "/var/db/gitup",
},

"ports" : {
"host" : "github.com",
"repository" : "/freebsd/freebsd-ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
],
},

"quarterly" : {
"host" : "github.com",
"repository" : "/freebsd/freebsd-ports.git",
"branch" : "quarterly",
"target" : "/usr/ports",
"ignores" : [
"distfiles",
"packages",
]
},

"release" : {
"repository" : "/src.git",
"branch" : "releng/11.4",
"target" : "/usr/src",
"ignores" : [
"sys/amd64/conf",
"sys/arm64/conf",
"sys/i386/conf",
"sys/pc98/conf",
"sys/powerpc/conf",
"sys/riscv/conf",
"sys/sparc64/conf",
]
},

"stable" : {
"repository" : "/src.git",
"branch" : "stable/12",
"target" : "/usr/src",
"ignores" : [
"sys/amd64/conf",
"sys/arm64/conf",
"sys/i386/conf",
"sys/pc98/conf",
"sys/powerpc/conf",
"sys/riscv/conf",
"sys/sparc64/conf",
]
},

"current" : {
"repository" : "/src.git",
"branch" : "main",
"target" : "/usr/src",
"ignores" : [
"sys/amd64/conf",
"sys/arm64/conf",
"sys/i386/conf",
"sys/pc98/conf",
"sys/powerpc/conf",
"sys/riscv/conf",
"sys/sparc64/conf",
]
}
}

[Graham Perrin]

… try for a gitup.conf file …

I'm watching <https://github.com/johnmehr/gitup/blob/main/gitup.conf>.

The most recent change:
<https://github.com/johnmehr/gitup/commit/0f52d593cfab2e7ef16439018232b37e8f6aa311#diff-39bd767a59a3138594332fbe99b51c0e531831ee92817e389b3435e1dd1474f9>

[Ed Maste]

Post by Arthur Barlow
Anyone know when portsnap will be able to work with the new ports tree on
github?

Work is in progress to convert the portsnap build infrastructure to
git. The changes are just about ready for testing, but it will
probably be a couple of days yet before it is deployed.