Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41722 - [go] Use source archive rather than full repository clone

Attached to Project: Community Packages
Opened by Florez Brownlee (frownlee) - Wednesday, 27 August 2014, 19:17 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 18 September 2014, 19:53 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Vesa Kaihlavirta (vegai)
Alexander F. Rødseth (xyproto)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Google code provides tar.gz snapshots for hg repository tags (i.e. https://go.googlecode.com/archive/go1.3.1.tar.gz). Since the PKGBUILD isn't meant to track code changes at the changeset level, I think it makes sense to use the archives instead of a full hg clone (the snapshot is less than 10% the size and is much quicker to download).

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Thursday, 18 September 2014, 19:53 GMT
Reason for closing:  None
Additional comments about closing:  Perhaps for a future release of Go. Perhaps.
Comment by Doug Newgard (Scimmia) - Thursday, 28 August 2014, 03:24 GMT
It was switched intentionally because of  FS#38860  and  FS#38597 . Do you have a way to work around these using the snapshot?
Comment by Florez Brownlee (frownlee) - Friday, 29 August 2014, 20:06 GMT
I'm probably being an idiot, but I'm not seeing the connection to those bug reports.

One think I should note is the snapshot I'm suggesting is NOT the release source tarball, but google code's automated snapshot of the hg tag. That is, the contents of that tarball are exactly the contents of an mercurial clone.
Comment by Alexander F. Rødseth (xyproto) - Saturday, 30 August 2014, 15:32 GMT
Thanks for filing a feature request.

Slightly longer packaging time is a small tradeoff for fetching the source code as directly from upstream as possible.
Most users won't compile the go package themselves, but install it from [community].

If people wish to compile the go package themselves, one would think that they would prefer the very latest hg version, compiling it manually or by using the go-hg package from AUR.

I think the current situation is preferable to the proposed alternative.
Comment by Alexander F. Rødseth (xyproto) - Thursday, 18 September 2014, 19:52 GMT
Using a tarball that is a snapshot of the hg tag is a good suggestion, but I don't see it making much of a difference. There are no gains for users that use the binary package, and only minor gains in term of package building speed for us.

Perhaps for a later version of the Go package.

Loading...