[Bug 199052] [PATCH] Use 7 alphanumeric GH_COMMIT for WRKSRC, related to "legacy.tar.gz" (codeload) GitHub backend method

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Apr 1 16:26:40 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199052

--- Comment #3 from lightside <lightside at 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.


More information about the freebsd-ports-bugs mailing list