On 03/07/2010 07:49 AM, Thomas Bächler wrote: > > This comes up every month at least (not necessarily on the mailing list, > but somewhere) and people always say "use git" without even thinking how > that would work - so far, nobody has ever presented a workflow that > would match our packaging requirements and was based on git. We don't > use SVN for fun - using SVN is everything but fun. > > 1) We want to be able to see which PKGBUILD matches the package in the > repository. In SVN, we use copy - which is subversion's equivalent to > branching: By copying, you create a reference and all history of the > copied file is still there. In git, copying means that the copy has no > history, it is entirely unrelated to the original. The only equivalent > in git would be branching - but you cannot branch a single file or path, > you can only branch the entire tree. > 2) Partial checkouts and commits: We check out single directories and > most importantly we commit to single directories without updating the > rest of the repository. These operations come naturally to SVN, but they > are against the very concept of git. > > The only viable solution I could think of is using one git repository > per package - and that is just crazy. > If it ain't broke..... don't fix it! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
