Mail Archives: geda-user/2012/11/20/16:31:00
On Nov 20, 2012, at 5:47 AM, Rupert Swarbrick wrote:
> Kai-Martin Knaak <kmk AT familieknaak DOT de> writes:
>> John Doty schrieb am 18. November 2012:
>>
>>>> My git cvs-import is s s s s o o o o s s s l l l o o o o w w
>>>> w w w
>>>
>>> That's not what I'm talking about, and I don't understand why you
>>> would want to import the whole gedasymbols website into your git
>>> repository.
>>
>> Because other users do viable symbols and footprints, too. And because I
>> don't want to loose access to said symbols and footprints if a storm
>> hits some place on the other side of the globe.
>
> I think you guys might be talking past each other. I'm a bit of a git
> fanboy, but I've been following this discussion quite closely and I
> think I understand DJ's point of view.
>
> As far as I can see, Kai-Martin is concerned with the possibility of
> gedasymbols going down and also with integrating his local git
> development tree with the stuff uploaded to gedasymbols.
He's already got that, as he has set up a git mirror. But wants to be able to upload to the main repository via git. That collides with the simple permissions-based submodule model that gedasymbols uses.
>
> John's point is that other people's symbols/footprints don't logically
> need to be in ones own development tree. If I understand him correctly,
> his model of how gedasymbols works is that you make symbols and
> footprints on your machine and then when you upload them to gedasymbols,
> you're basically publishing them. Then the versioning that CVS allows
> isn't particularly relevant, but doesn't hurt.
Yes.
But there's a piece you've missed: the current repository has, in git terms, 62 submodules, one for each author. Each author's access is restricted by file permissions. The submodule structure transparent to the user unless they attempt to trespass. While git has submodules, they have some subtle properties, and are not so transparent.
>
> Please tell me if I've got your positions wrong!
>
> Now, as far as I can see, it's not too difficult to make both of you
> happy :-)
>
> CVS is indeed slow, but presumably no-one needs the development history
> for others' symbols. As such, DJ could stick a cron job on
> gedasymbols.org that makes a downloadable snapshot of the current
> repository (minus CVS directories) once a day. Then people using git
> could just download "the rest" in one go.
>
> I'm not sure how big the entire lot is, but if it's enormous, maybe it
> would be worth setting up rsync. I wouldn't bother if the repository is
> under 10mb though.
>
> With this easy change, we're still using CVS. Developers can set up
> their accounts to just push to the CVS subdirectory, which will be very
> quick. But it's easy to have a personal copy of the entire contents.
> (off-continent backups, yeah!)
The way I use it, I have that. "cvs update -d" takes a few minutes, but so what?
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -