That would be nice. This would also solve my problems with "poudriere".
Code:
poudriere ports -c -B 2021Q1 -m git+https -p 2021Q1That would be nice. This would also solve my problems with "poudriere".
poudriere ports -c -B 2021Q1 -m git+https -p 2021Q1Yes it is: /usr/local/share/poudriere/common.sh
7581 : ${SVN_HOST="svn.freebsd.org"}
7582 : ${GIT_BASEURL="github.com/freebsd/freebsd.git"}
7583 : ${GIT_PORTSURL="github.com/freebsd/freebsd-ports.git"}
7584 : ${FREEBSD_HOST="https://download.FreeBSD.org"}I was going to recommend someone participating in the thread make a Tutorial out of their efforts to save answering the same question over and over.
If it helps, whilst you wait:
www.captiongenerator.com
I prefer this doesnt become another what ports tool to use thread as lately on here there seems to be a campaign to get people to move over to the newer tools, but I will post a summary of why its my preference, although I dont use it on every server.
Last SVN commit to the ports tree:
[ports] Revision 569609
svnweb.freebsd.org
So make sure to change your local ports trees if you've been using subversion to update it. portsnap(8) users should not be impacted by this change.
I don't think You're much wrong - only, I would rather pronounce it as "working with it". It is the difference between business customers (B2B) and consumers (B2C).
In this context, it is also interesting to see how the FreeBSD motto changed over the years.
"Best suited tool"? I strongly beg to differ.
pkg repo /root/repo/pub.key"), all distributed by Apache.
Yeah right.So that's why Git got mentioned in the handbook long before the whole transition had been finished.
See my point above.
commit a3ad91f11fea5cc457eb053c46c26e4dd43df599
Author: Rene Ladan <rene@FreeBSD.org>
Date: Tue Apr 6 20:59:06 2021 +0200
Handbook: adjust for the various git migrations.
- prefer to install git as a package over building it oneself.
- update dates in in the introduction
- let some Subversion URLs move to the src repository, as it is the only
repository with an Subversion exporter active.
- let the user install git instead of subversion for doing ports work.
Reviewed by: emaste, mat
Differential Revision: https://reviews.freebsd.org/D29450commit abff932fe818c144380fd5ebfdcdf44f93de46de
Author: Warner Losh <imp@FreeBSD.org>
>>> Date: Tue Mar 16 21:55:44 2021 -0600
Merge in the migration from subversion / github
Add in the migrating from the old subversion / git docs. This section
should be removed in a few months maybe.
Contributions by: lwshu@, Alexander Richardson, kib@, Ceri Davies
[...]
commit cf77cf8be5142f3069e313f6eef3a36597b3dab3
Author: Li-Wen Hsu <lwhsu@FreeBSD.org>
>>> Date: Tue Jan 12 00:46:00 2021 +0800
Update information of source code repositories
Doc and src repositories are in git now and ports tree is in progress.
Reviewed by: uqs, ygy
Approved by: ygy
Differential Revision: https://reviews.freebsd.org/D28080
[...]
commit f3bf61d5614d54621681c2613edfa77c3eb659db
Author: Li-Wen Hsu <lwhsu@FreeBSD.org>
>>> Date: Thu Jan 7 17:13:44 2021 +0800
Add link to git pepository
Approved by: ygy
Differential Revision: https://reviews.freebsd.org/D28015
[...]
commit e98cc8974139ae77d1550f60dba75e3d7435915d
Author: John Baldwin <jhb@FreeBSD.org>
>>>> Date: Mon Dec 21 11:07:24 2020 -0800
Generate links to cgit instead of svn in document title blocks.
PR: 251940
Reviewed by: emaste, gjb, ygy
Differential Revision: https://reviews.freebsd.org/D27704I'd argue that Poudriere is a widely used tool when people want to maintain their own package repository. I don't see many people installing Poudriere just for the sake of installing a single port.
I'm actually not too sure about this to be honest. From my point of view the only reason we have a compiler onboard is because src is a part of the whole distribution. When installing FreeBSD you can opt to have the Ports collection and source tree installed as well. But what good would those be without a compiler?
Huh? Ever heard of freebsd-update(8)? It's "only" the de-facto way to upgrade your system, no biggie. It even allows you to customize its settings where you can opt-out from specific parts such as the ports collection and/or the source tree (as well as world/games ? )
Here's a voice that says: stop throwing wild statements around without any arguments to back up your claims.
It's not about making a difference in the first place, it's about trying to help out. "Making a difference" makes it sound like a popularity contest, yech!
What a load of nonsense.
What are you about?
The first post on the thread indicated that portsnap should not be impacted. I think I'm seeing the same thing as in your separate thread, i.e. portsnap not updating the ports tree. I take it you didn't find a solution to continue using Portsnap?
Last SVN commit to the ports tree:
[ports] Revision 569609
So make sure to change your local ports trees if you've been using subversion to update it. portsnap(8) users should not be impacted by this change.
Create an alias for the Portsnap command using the git in your environment.
Portsnap will continue to be supported. It is deprecated, but it will continue to work for several years, probably. Note that FreeBSD 13 ships with portsnap, too (and it’s even still in 14-current).
