Re: When will git be supported for ports?
Hi! > > https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html > > The https://github.com/bsdimp/freebsd-git-docs/ material > for git-why.md is still available via: > > https://github.com/bsdimp/freebsd-git-docs/commits/483527525db5cd7cf27141a2ca21059d9a3b158e/git-why.md > > It had commits on 2020-Oct-20, 2020-Dec-02, and 2020-Dec-03. So > it was updated a little from the 2020-Sep blog variant. The > changes may not be important. I've not gone through them. Thanks -- how did you find the commit hash / link and the dates ? It's the old saying: Give a man a fish, so he will not be hungry for a day, teach him to fish and he will be fed for a livetime 8-} -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
Kurt Jaeger pi at freebsd.org wrote on Wed Apr 28 19:30:32 UTC 2021 : > > > > The 'why' was explained here: > > > > > > > > https://github.com/bsdimp/freebsd-git-docs/ > > Ah, here's the link to the 'why' post: > > https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html The https://github.com/bsdimp/freebsd-git-docs/ material for git-why.md is still available via: https://github.com/bsdimp/freebsd-git-docs/commits/483527525db5cd7cf27141a2ca21059d9a3b158e/git-why.md It had commits on 2020-Oct-20, 2020-Dec-02, and 2020-Dec-03. So it was updated a little from the 2020-Sep blog variant. The changes may not be important. I've not gone through them. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
Hi! > > > The 'why' was explained here: > > > > > > https://github.com/bsdimp/freebsd-git-docs/ Ah, here's the link to the 'why' post: https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
Hi! > > The 'why' was explained here: > > > > https://github.com/bsdimp/freebsd-git-docs/ [...] > That was a draft repository used before the document migrated to use AsciiDoc. > > These changes have been pushed into the FreeBSD tree. See the committer’s > guide. > https://docs.freebsd.org/en/articles/committers-guide/#git-primer Yes, I've seen this link. Unfortunatly, I have not yet found the part in that new git-primer where the 'why git' was explained as it was in the previous text. -- p...@freebsd.org +49 171 3101372 Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
On 2021-04-28 11:25, Li-Wen Hsu wrote: On Thu, Apr 29, 2021 at 2:15 AM Kurt Jaeger wrote: Hi! > Maintainer for some ~160 ports, and attempting to fix some > bugs. But as I understand it 'git' is supposed to be the new > source of truth. While I know svn by heart. I have near zero > understanding of git, or for that matter, why anyone would > rather use it. The 'why' was explained here: https://github.com/bsdimp/freebsd-git-docs/ But, unfortunatly, that text moved somewhere. It's a good first test to find out how to recover that text from the git repo 8} Any hints ? That was a draft repository used before the document migrated to use AsciiDoc. In the README of that repository: """ These changes have been pushed into the FreeBSD tree. See the committer’s guide. https://docs.freebsd.org/en/articles/committers-guide/#git-primer """ > That said; as I try to discover the new > procedures for maintaining ports under git. I see there isn't > anything in the porters-handbook regarding the acquisition > of the ports tree in order to get started. I guess that was because the porter's handbook was mainly about porting, like writing the Makefile and pkg-plist. The VCS thing was mainly in the committer's guide. But it's nice to mention some simple git usages which will help people submit patches. After all that's one of the reasons and possible benefit to use git. A HUGE thank you for your reply. I know this probably seems simplistic. But in order to get involved with ports, you're going to need a ports tree. Not everyone who starts using FreeBSD will have a source tree, or even build from source. So getting the ports tree as a necessary first step IMHO should be noted. As everyone seems to be telling everyone the proper git workflow, and they all vary. Maybe FreeBSD might show a 'ports git workflow'. Much the same as the build/install world/kernel workflow in /src/UPDATING at the top of the porters-handbook? It's not that I don't know how to 'git clone'. It's that there's a preferred procedure/protocol to becoming/being a FreeBSD ports Maintainer, and I simply want to get it right the first time. Thereby saving committers a good deal of time and effort. ;-) Thanks again! :-) --Chris > Shouldn't this be at the very beginning of the ports doc? This below should work, and I agree with you: It was hard to find out. mkdir -p somedir/ports cd somedir git clone -o freebsd \ --config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \ https://git.freebsd.org/ports.git ports I'm also trying to learn more git to be able to work on the ports tree, but my time is limited and somehow, I still do not see the forest for the trees 8-( ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
On 2021-04-28 11:15, Kurt Jaeger wrote: Hi! Maintainer for some ~160 ports, and attempting to fix some bugs. But as I understand it 'git' is supposed to be the new source of truth. While I know svn by heart. I have near zero understanding of git, or for that matter, why anyone would rather use it. The 'why' was explained here: https://github.com/bsdimp/freebsd-git-docs/ But, unfortunatly, that text moved somewhere. It's a good first test to find out how to recover that text from the git repo 8} Any hints ? That said; as I try to discover the new procedures for maintaining ports under git. I see there isn't anything in the porters-handbook regarding the acquisition of the ports tree in order to get started. Shouldn't this be at the very beginning of the ports doc? This below should work, and I agree with you: It was hard to find out. mkdir -p somedir/ports cd somedir git clone -o freebsd \ --config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \ https://git.freebsd.org/ports.git ports I'm also trying to learn more git to be able to work on the ports tree, but my time is limited and somehow, I still do not see the forest for the trees 8-( Kurt, you're AWESOME! Vastly useful, and GREATLY appreciated. :-) Now, if we could only get this $hit in the docs. ;-) Thanks! --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
On Thu, Apr 29, 2021 at 2:15 AM Kurt Jaeger wrote: > > Hi! > > > Maintainer for some ~160 ports, and attempting to fix some > > bugs. But as I understand it 'git' is supposed to be the new > > source of truth. While I know svn by heart. I have near zero > > understanding of git, or for that matter, why anyone would > > rather use it. > > The 'why' was explained here: > > https://github.com/bsdimp/freebsd-git-docs/ > > But, unfortunatly, that text moved somewhere. It's a good > first test to find out how to recover that text from the git repo 8} > Any hints ? That was a draft repository used before the document migrated to use AsciiDoc. In the README of that repository: """ These changes have been pushed into the FreeBSD tree. See the committer’s guide. https://docs.freebsd.org/en/articles/committers-guide/#git-primer """ > > That said; as I try to discover the new > > procedures for maintaining ports under git. I see there isn't > > anything in the porters-handbook regarding the acquisition > > of the ports tree in order to get started. I guess that was because the porter's handbook was mainly about porting, like writing the Makefile and pkg-plist. The VCS thing was mainly in the committer's guide. But it's nice to mention some simple git usages which will help people submit patches. After all that's one of the reasons and possible benefit to use git. > > Shouldn't this be at the very beginning of the ports doc? > > This below should work, and I agree with you: It was hard to find out. > > mkdir -p somedir/ports > cd somedir > git clone -o freebsd \ > --config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \ > https://git.freebsd.org/ports.git ports > > I'm also trying to learn more git to be able to work on the > ports tree, but my time is limited and somehow, I still do > not see the forest for the trees 8-( ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When will git be supported for ports?
Hi! > Maintainer for some ~160 ports, and attempting to fix some > bugs. But as I understand it 'git' is supposed to be the new > source of truth. While I know svn by heart. I have near zero > understanding of git, or for that matter, why anyone would > rather use it. The 'why' was explained here: https://github.com/bsdimp/freebsd-git-docs/ But, unfortunatly, that text moved somewhere. It's a good first test to find out how to recover that text from the git repo 8} Any hints ? > That said; as I try to discover the new > procedures for maintaining ports under git. I see there isn't > anything in the porters-handbook regarding the acquisition > of the ports tree in order to get started. > Shouldn't this be at the very beginning of the ports doc? This below should work, and I agree with you: It was hard to find out. mkdir -p somedir/ports cd somedir git clone -o freebsd \ --config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \ https://git.freebsd.org/ports.git ports I'm also trying to learn more git to be able to work on the ports tree, but my time is limited and somehow, I still do not see the forest for the trees 8-( -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
When will git be supported for ports?
Hi all, Maintainer for some ~160 ports, and attempting to fix some bugs. But as I understand it 'git' is supposed to be the new source of truth. While I know svn by heart. I have near zero understanding of git, or for that matter, why anyone would rather use it. That said; as I try to discover the new procedures for maintaining ports under git. I see there isn't anything in the porters-handbook regarding the acquisition of the ports tree in order to get started. Shouldn't this be at the very beginning of the ports doc? The closest thing I could find was a reference to a link: #ports-using/ in the Handbook. Which doesn't exist. It *should* throw a 404. But was cleverly masked, and simply returns the front page. This is a terrible idea. As the doc maintainers will never know they need to make corrections, and new users with a new interest in FreeBSD will become frustrated and turn away. Maintainers, like me, utilizing what little time they have to spare will also become frustrated and likely find that they now only have the time to discover where the actual information is. With no more time to actually *fix* the port they sought to. While I realize this should probably be sent to docs@ I'm not on the list, and because this is ports related. I hope it finds value here as well. Thanks for listening. --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Python update 3.7->3.8
On Wed, 28 Apr 2021 03:25:02 -0600 "@lbutlr" wrote: > > This long command hanle files that requires shebang: > > portmaster -BvD -y --no-confirm --delete-build-only `grep -rsp > > "\/python3\.7" /usr/local/ | grep -v '/usr/local/man/' | grep -v > > '/usr/local/lib/python3' | sed -e 's|:.*||' -e 's|Binary file ||' > > -e 's| matches||' | xargs pkg which -oq | sort -u` > > What grep are you using? > > /usr/bin/grep -rsp "python3\.7" /usr/local/ => grep: invalid option > -- p > > (FreeBSD 12.2, grep (GNU grep) 2.5.1-FreeBSD) > WITH_BSD_GREP= # Install BSD-licensed grep as '[ef]grep' instead of GNU grep. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Python update 3.7->3.8
On 26 Apr 2021, at 20:43, Rozhuk Ivan wrote: > This long command hanle files that requires shebang: > portmaster -BvD -y --no-confirm --delete-build-only `grep -rsp "\/python3\.7" > /usr/local/ | grep -v '/usr/local/man/' | grep -v '/usr/local/lib/python3' | > sed -e 's|:.*||' -e 's|Binary file ||' -e 's| matches||' | xargs pkg which > -oq | sort -u` What grep are you using? /usr/bin/grep -rsp "python3\.7" /usr/local/ => grep: invalid option -- p (FreeBSD 12.2, grep (GNU grep) 2.5.1-FreeBSD) -- Margo: Although Dark King is a little generic as far as villain names go, wouldn’t you say? Eliot: I have notes. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
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 can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/exult | 1.7.0.20210424 | snapshot-v1.7.0.20210428 +-+ lang/retro12| 2021.2 | 2021.4 +-+ textproc/html-pretty| 1.01| 1.02 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
