Am 23.06.2012 um 00:07 schrieb David R. Morrison: > > On Jun 22, 2012, at 10:59 AM, Alexander Hansen wrote: > >> Any thoughts about moving dists/ over to github? >> >> Even though sourceforge isn't going to close down CVS access, it'd be >> nice to move to a more modern system. Plus, for users behind firewalls, >> github allows files to be accessed via https--we're doing pretty much >> the best we can with proxy support for CVS, but sometimes that's still >> blocked. >> >> And for big updates, like a new OS version, I believe it's easier to >> handle a branch to do changes in git than in CVS (I'm not sure about >> that, though). > > This is as good a time as any to think about making such a change, but of > course it would take some time to implement (i.e., its not going to be ready > for the imminent release of 10.8). > > The reason I say this is that we would need to write a selfupdate-git > function, and work through issues like how it interacts with selfupdate-cvs, > whether we are migrating everything or just the most recent tree or trees, > etc. etc.
Actually, Daniel Johnson has been working on this: <https://github.com/danielj7/fink/tree/selfupdate-git>. In the end, it's a matter of committment: DO we *want* to switch to this? Does it pay off for Daniel and others to invest blood and tears into it? Because if it's not clear whether this work has a good chance of being merged in the end, then it's a bit difficult to motivate oneself to work on it... My stance is clear on this: I *want* selfupdate-git, and I really want to stop using CVS for anything. The sooner the better. I'll make our life a lot easier. While I am at it, I'd also like to see us switch to the new dpkg / apt etc. ;) I think it was Sjors who worked on that. As for whether to host git repositories. on SF.net or github: that's a mostly irrelevant question. We can easily host on both. It's a trivial matter to switch between them. But github offers so many useful features that SF.net misses that it's not even a close contest. Add in the fact that SF.net tends to leave bug reports and feature requests untended for years in a row, then closes them saying "we are now deprecating this function" etc., makes me not want to host *anything* anymore on SF.net unless I have no other choice. But that's just me. If others want to host git repositories on SF.net (or bitbucket, or gitorious, or Google Code, or on a private server, or, or, or), that's all fine by me -- after all, one of the big advantages of DVCS like git and mercurial is that everybody gets a full copy of the repository; and which repository is the "upstream" of which other repository is something that can be changed in a blink of an eye ;). Cheers, Max ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
