Could we be allowed to commit .gif and .tar.gz (or .tgz)? Reminder: add types in CVSROOT/checkxml.pl =~ /((\.(xml|xsl|txt|pdf|html|rdf|dtd|log|sxi|css|png|jpg))|changelog)$/i ) { ... print "Allowed filetypes are:\n"; print "xml|xsl|txt|pdf|html|rdf|dtd|log|sxi|css|png|jpg and changelog\n\n";
On the tarballs....any reason we couldn't continue to leverage our mirror infrastructure? With a few exceptions, all of our tarballs are distributed from there since it has much better bandwidth, availability and scalability.
Why don't you `emerge gif2png`?
We already have gif pics on our site and they do have advantages over png/jpg in some cases. Look at the blocked bug. We are reformatting and hosting previously published articles (Bug 95661). We have been allowed to and we do not alter the content of those articles. The Posix articles have a gif and a small tar with code samples. Those belong to the articles, we simply need to publish them all together.
gifs are allowed now. And for tar-files, take Kurt's statement in comment #1.
(In reply to comment #1) > On the tarballs....any reason we couldn't continue to leverage our mirror > infrastructure? With a few exceptions, all of our tarballs are distributed from > there since it has much better bandwidth, availability and scalability. Fair enough. Where do we put the tarball that belongs to that article? How do we put it there? How do we make sure it stays there?
I'm not opposed to distributing tarballs from www.g.o, but I want to make sure they're very limited and only for things specifically related to the web site. Lars, is there any easy way to allow tarballs to only be committed to a specific directory? gentoo/xml/htdocs/downloads/ or something? Then we can at least easily track what is stored there.
(In reply to comment #6) > Lars, is there any easy way to allow tarballs to only be committed to a specific > directory? gentoo/xml/htdocs/downloads/ or something? Then we can at least > easily track what is stored there. It would be the easiest way to place tar-balls on the webpage, but storing them in CVS is something it has not been designed for... And I oppose to add them into the [gentoo] repository. Let's create a separate one, so that devs with a bad connection don't whine that they have to download large tar-balls during an cvs up.
(In reply to comment #7) > And I oppose to add them into the [gentoo] repository. Let's create a separate > one, so that devs with a bad connection don't whine that they have to download > large tar-balls during an cvs up. Consider them like files for an ebuild. Any tarball bigger than 20-50k shouldn't be here....and I don't expect we'll have many of these. IMHO, why create something seperate for this? You could maybe restrict commit access to only docdevs and we'll check internally to ensure nothing bigger than the limit gets pushed? Of course, infra's call...thought I'd put my 2 cents worth.
(In reply to comment #7) > It would be the easiest way to place tar-balls on the webpage, but storing them > in CVS is something it has not been designed for... I don't give a toss whether the file is in CVS or not. All we need is to publish that file with the article, link it from the article, be sure it will stay wherever it's been put and forget about it. Feel free to give me another way to put a file on www.g.o > And I oppose to add them into the [gentoo] repository. Let's create a separate > one, so that devs with a bad connection don't whine that they have to download > large tar-balls during an cvs up. Another repository that the web nodes have to sync? For one file? You realise we're talking about a 3 Kbytes file that is not going to change? If you're so much worried about others abusing this, just restrict tarballs to /doc/en/files and even add an extra check on size<5K if you feel like it.
(In reply to comment #9) > Another repository that the web nodes have to sync? For one file? > You realise we're talking about a 3 Kbytes file that is not going to change? > If you're so much worried about others abusing this, just restrict tarballs to > /doc/en/files and even add an extra check on size<5K if you feel like it. Your request sounded like adding a lot of tar-balls with a huge size. How should I guess what you want to add? Go forward and commit.
