[aur-general] Fwd: please add -depth 1 to makepkg git clone
tailinchu at gmail.com
Sat Apr 6 03:25:37 EDT 2013
A rage post with too many typos and not enough punctuation is hard to read.
>This is dumb because using cp is not enough, you should be using git clone because it is git and straight from git, if you goal is to just use the newest you are doing it wrong go write you own pkgbuild.
What is not enough? cp has option to reserve everything.
>The only reason to use git packages is if you are deving upstream and want to actively test development of upstream packages... Or if up stream is dumb enough to never tag stable releases. Fortunately there are very few of the latter, so to support the majority of of users we clone the whole thing.
Please read document for depth=1 and shallow clone. When we create a
package, we only need the snapshot at that time; we rarely revert any
commit. After we do shallow clone, we can still pull, and remake
package. I really dont understand your reason for " to support the
majority of of users we clone the whole thing" because shallow clone
>I truly do not understand why this conversation exists. We discussed this months ago. The conclusion was that you really shouldn't be using these packages unless you are following upstream...
yes, i agree with you. But as a person who commits patches and needs
to test, I think using --depth 1 makes initial cloning faster and
decreases the load of remote git server. Think about this 100 people
clones vlc.git with shadow (around 600mb) vs without shadow (around
10000mb)... its not just about whether you care it or not; please
preserve resources of other projects.
On Fri, Apr 5, 2013 at 10:50 PM, Daniel Wallace
<danielwallace at gtmanfred.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Tai-Lin Chu <tailinchu at gmail.com> wrote:
>>1. you can still pull, so it will not be a reason to go against it
>>>This is also true. makepkg clones a bare repository to the SRCDEST
>>>directory. If this is a shallow bare repo, then clones cannot be made
>>>it which is what makepkg does.
>>2. ... i dont think why it needs to use git clone. using cp is good
>>On Fri, Apr 5, 2013 at 7:05 PM, William Giokas <1007380 at gmail.com>
>>> On Fri, Apr 05, 2013 at 06:47:55PM -0700, Tai-Lin Chu wrote:
>>>> makepkg only needs the latest git snapshot
>>>> there are only 2 cases that wont work:
>>>> 1. revert git commit
>>>> 2. count # of revisions
>>>> > Won't work as you can't clone shallow repositories, which makepkg
>>>> > needs to do to create the working copy for the build.
>>> This is also true. makepkg clones a bare repository to the SRCDEST
>>> directory. If this is a shallow bare repo, then clones cannot be made
>>> it which is what makepkg does.
>>> William Giokas | KaiSforza
>>> GnuPG Key: 0x73CD09CF
>>> Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
> I truly do not understand why this conversation exists. We discussed this months ago. The conclusion was that you really shouldn't be using these packages unless you are following upstream... What if the current depth=1 is unstable and has a huge bug.... Then what... Oh those users aren't following upstream and have no idea because instead of the developers of the program monitoring and telling them this a stable (and hopefully bug free release... The use your depth=1 pkgbuild and never update until one of the depends does a soname bump and breaks everything... To save space... In my opinion we should actually remove git packages from the aur... It adds an air of instability to the distribution... People that use -git should really maintain there own pkgbuild... And yes I felt this was so important I interrupted my night out to send...
> So, unlike you, I hope depth is never supported in package source=()
> - --
> Sent from my Android Phone.
> Daniel Wallace
> Arch Linux Trusted User
> -----BEGIN PGP SIGNATURE-----
> Version: APG v1.0.8
> -----END PGP SIGNATURE-----
More information about the aur-general