5 ms·
Seems like it's time to host it on a DVCS service so the problem won't be so disruptive again.
by kevin_thibedeau 10y ago
Seems like it's time to host it on a DVCS service so the problem won't be so disruptive again.
- CydeWeys 10y agoYeah. It's still on CVS. May as well throw it up on GitHub like every other open source project. That doesn't have to be its only home on the web, but at least it would always be available there. The main open source project I work on (Pywikibot) isn't primarily hosted on GitHub, but it is mirrored there.
- japaget 10y agoGithub mirror is at https://github.com/vadz/libtiff https://github.com/vadz/libtiff .
- alrs 10y agoRemember sunsite.unc.edu? Sourceforge? Both were the gonna-be-around-forever source code distribution points of their day.
- sedachv 10y ago> Remember sunsite.unc.edu? That's a throwback. I looked it up and apparently UNC's Sunsite turned into http://www.ibiblio.org/about/ http://www.ibiblio.org/about/ There are a couple of other Sunsites still up. This one looks like it has not been updated since 1997: http://sunsite.ubc.ca/ http://sunsite.ubc.ca/
- tropo 10y agoNah, sunsite is a noob, along with Slackware. When you wanted to download boot/root, Tamu, or SLS you went to tsx-11.mit.edu or ftp.funet.fi to get it.
- flukus 10y agoWhich is why a DVCS is important, the history goes with every copy.
- kasey_junk 10y agoA history goes with every copy. You still need a protocol for determining the history.
- cyphar 10y agoIf you have a maintainer who signs their commits, you trust their signatures and call it a day. Go with the latest commit and that tells you the history that they have cryptographically claimed is "correct".
- Someone 10y agoOne problem I see there is that, with git, you still have to take care that you keep around all the commits that at any given point in time were declared "correct". For example, if a commit is amended and force pushed out to remove a backdoor from a popular package, a site interested in the history of the library will want to ensure that the faulty commit stays around. I'm not even sure that is 100% possible, but it, at least, will take some careful git configuration.
- cyphar 10y agoYou never rewrite published history with git. It's fine to force push signed git commits to a random branch that are going to be rewritten -- that's just how development works. But when you merge something, it stays that way. Touching history in release branches is something that will always end in tears (all of the tagging breaks, everyone's clone will complain when they update it, etc). Just bad news all around. As for a site which cares about archiving, they can almost certainly add a tag for every commit they slurp up (making sure it doesn't get hit by the git gc). Though, I'm fairly sure that you can just configure your git instance to never garbage collect.
- flukus 10y ago> You still need a protocol for determining the history. Is this a real problem or a theoretical problem?
- ashitlerferad 10y agoSourceforge still exists. sunsite.unc.edu merged into ibiblio.