Date: Wed, 01 Apr 2015 16:26:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199052] [PATCH] Use 7 alphanumeric GH_COMMIT for WRKSRC, related to "legacy.tar.gz" (codeload) GitHub backend method Message-ID: <bug-199052-13-W2Uyj8zVFi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199052-13@https.bugs.freebsd.org/bugzilla/> References: <bug-199052-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199052 --- Comment #3 from lightside <lightside@gmx.com> --- (In reply to comment #2) > but some not, if there is a need to use full commit hash, i.e. very long directory name for WRKSRC. Realistically, the need for full commit hash may be rare (to this time). Even creation of repository with many commits takes time. Personally, I didn't find abbreviated commit hash, which equals to full commit hash for some existing large repositories. But this is logical conclusion to use full commit hash, if you may want your download method works for previous versions of port, independent from future changes to repository. What I said may be not related to concrete "legacy.tar.gz" or "tar.gz" GitHub backend methods. Technically, they are the same, but with different output, I guess. I think, the possible issue with long name for WRKSRC directory is solvable with renaming to short directory name, e.g.: WRKSRC= ${WRKDIR}/${PORTNAME} # ... post-extract: @(cd ${WRKDIR} && ${MV} ${GH_PROJECT}-* ${PORTNAME}) But this is what "legacy.tar.gz" GitHub backend method (potentially) does in result. In other words, there are solutions, independent from where current ports framework takes its development. If ports framework doesn't fit (or help), it's possible to create own proper methods, when needed. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199052-13-W2Uyj8zVFi>