-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 28/08/13 01:39 PM, Michał Górny wrote:
> The question would be: do you feel like we should really provide a
> verbatim clone of upstream's repository? Or should we focus on the
> eclass' main goal, that is fetching the remote sources in the most
> bandwith and space-efficient manner?
+1 on the second one -- eclasses are first and foremost to support
ebuilds, and unless ebuilds need access to multiple branches at the
same time or some other rather odd and non-straight-forward git trick
that would require a full clone, all we should worry about doing is
providing a way to get that shallow clone of only that code snapshot
that the ebuild needs to build.
As a bit of a tangent, if an end-user has their own local clone of a
repository and uses ${PN}_LIVE_REPO to point to it (or if they have a
custom out-of-tree ebuild that only has a local URI), it might be nice
to detect that and skip the fetch so that a checkout can be done from
it directly into ${S} rather than doing the extra copy...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iF4EAREIAAYFAlIeSl4ACgkQ2ugaI38ACPAzBAEAt5jDJA5uiB4AcS4wPWHjjZA0
LtqErcFZuF5kOYLzXSgA/24Oa7GxBguFrLQBWQJDt95IYz8Po76us4BVg4X6/wu8
=xrdH
-----END PGP SIGNATURE-----
