On Fri, Sep 3, 2010 at 5:15 AM, Benjamin Podszun <benjamin.pods...@gmail.com> wrote: > Hi. > > On Fri, Sep 3, 2010 at 4:34 AM, Katie Sangha <katie.san...@gmail.com> wrote: >> Has there been any progress on making a deb package in the last couple >> months? I went to install this and found a very length install doc. >> I'm sure the process could be improved a lot even if its not through >> apt. > > As far as I'm concerned, no package has been created. I do admit that > the process can be improved significantly though. For my own purpose I > modified the guide at [1] (works fine for me), because > - it did some things I didn't want (install phpmyadmin for one) > - it had lots of "emacs somefile and make sure it looks like this" steps > > I replaced the latter with > cat > /tmp/gitorious.yml << _EOF_ > My > config > here > _EOF_ > sudo mv /tmp/gitorious.yml /path/to/gitorious/for/me > > to make these steps copy&paste-able Most things don't need user > intervention and can be solved by either replacing/creating a file > during installation or with a simple sed line. > >> The link in the prior post appears to be broken now. > > See above: It's not for me? Was it a temporary thing only, maybe? > > 1: http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/
Sorry about the link from above. I had to do some moving and renaming on the server a few days ago. The original source code can be found at http://scm.bluequartz.net/eim/ei-guides When I wrote that guide there I was taking from the various instructions from around the internet and from gitorious itself. I am not a line command guru and so everything I do is with emacs mainly because that is the only text editor I ever learned commands for. I can edit the guide to say as much and remove the emacs part. This also comes from the point of view that you are installing on a brand new clean Ubuntu 10.04 server install and that you have complete control over the server. The whole thing could almost be done with a good shell script as there are only a few variables that really need to be filled in: username and passwords for MySQL, Gitorious, git system user. Where to install gitorious into. and where is your apache installation. I should also not the installation of phpmyadmin and how insecure that really is. Probably make that an optional install. It has helped me out a few time but I have since protected it behind a password protected web site. I'll probably end up uninstalling it here pretty soon. At one point I got a quote from a the company that does the "MAMP" installers on what it would take to get the same thing for Gitorious and they quoted about $10,000 which in my short experience here is about right. There are so many variables to get "right" that no 2 installs are the same. Change one of those variables above and every path in every script needs to change. What I should really do is place all the scripts and stuff into my branch on Gitorious (bluequartz-mainline) which would make the install easier and there would not have to be so much "emacs.. paste this.. " stuff in the guide. Thanks for the feedback. Mike Jackson www.bluequartz.net > >> On Jul 14, 6:31 am, Michael Jackson <imikejack...@gmail.com> wrote: >>> This was my experience setting up Gitorious on Ubuntu 10.04 LTS Server >>> >>> http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/... >>> >>> Mike Jackson >>> >>> On Jul 13, 2010, at 8:52 PM, Hedge Hog wrote: >>> >>> >>> >>> > On Wed, Jul 14, 2010 at 4:12 AM, Will Daniels >>> > <daniels.w...@googlemail.com> wrote: >>> >> Hello again :) >>> >>> >> Just spotted this thread has come back to life. Sorry I kind of >>> >> gave up >>> >> on it...just too many problems. First off is gem, which is >>> >> completely at >>> >> odds with apt and gitorious will need _all_ references to gem >>> >> eliminated >>> >> by the packaging. That much I accepted, though I didn't know about >>> >> the >>> >> gem issue initially. So I started topackageup the needed gems >>> >> individually, joined the ruby-extras team at Debian and got my >>> >> first gem >>> >>packageapproved there (oauth I think). >>> >>> >> But then I went on to rdiscount...I thought it all looked OK >>> >> license-wise so I went and did all the packaging for that then >>> >> noticed >>> >> it was using the 4-clause BSD license. So I contacted the author >>> >> (David >>> >> somebody) and asked if he would consider updating the license to the >>> >> newer 3-clause BSD that is compatible with DFSG. But he basically >>> >> said >>> >> he was already well aware of the issue with distro packaging but >>> >> didn't >>> >> want to change it and he is using the old 4-clause license >>> >> deliberately. >>> >>> >> Obviously BlueCloth is an alternative there, but I think I ended up >>> >> finding a few other problems and by the end of it I was changing >>> >> quite a >>> >> lot of the gitorious code to move things for FHS compliance, >>> >> deprecate >>> >> gem, change to Bluecloth and whatever else that it became quite a big >>> >> job and I soon ran out of time. >>> >>> > Sounds like this was a little painful. >>> > Gitorious is on my to do list, so I have not experienced an install. >>> > Nonetheless. >>> > If there are so many moving parts it might be easier to have a Chef >>> > and Puppet cookbook? >>> > In fact this was the plan of attack I had in mind when I got to trying >>> > Gitorious. >>> > The main reason was that a chef cookbook would allow for different >>> > configuration/usage scenarios to be specified, e.g. intall from repo's >>> > head vs a tar ball. >>> >>> > Has anyone tried setting up a chef/puppet cookbook? >>> >>> > Best wishes >>> >>> >> It's not that it's too impossible really, but the project at work I >>> >> wanted to use it for went down the tube and then I got ill for a >>> >> while >>> >> and I just never found the motivation again to pick it up afterward. >>> >> Though I'm still happy to help out a bit if somebody else wants to >>> >> take >>> >> up the gauntlet. >>> >>> >> It was always my intention to host it in a PPA on launchpad, there's >>> >> really only one line in the changelog that you need to update to >>> >> put a >>> >> Debianpackagein a PPA for Ubuntu. But since launchpad is only >>> >> integrated with Bazaar I don't see any value in hosting any other >>> >> part >>> >> of it there - it's just as easy to work with git using git- >>> >> buildpackage >>> >> etc. then dput *changes to upload the result to a PPA for the build. >>> >>> >> It would obviously be nice to get thepackageinto Debian proper, >>> >> which >>> >> would then go automatically into Ubuntu repos on the next sync, but I >>> >> might have been too optimistic to try to get everything properly >>> >> compliant with Debian from the start. Using a PPA would at least give >>> >> some flexibility to have it less-than-perfect but usable wrt FHS and >>> >> DFSG until everything is in place to send it for review. >>> >>> >> I'll have a look and see where I got to with it...might help to start >>> >> somebody else off. >>> >>> >> Cheers! >>> >> Will >>> >>> >> On 13/07/10 19:43, Benjamin Podszun wrote: >>> >>> On Tue, Jul 13, 2010 at 8:03 AM, Marius Mårnes Mathiesen >>> >>> <marius.mathie...@gmail.com> wrote: >>> >>> >>>> 2010/7/13 Jörg W Mittag <joergwmittag+r...@googlemail.com> >>> >>> >>>>> That's why I'd love to have Debianpackage. And I think the >>> >>>>> redMine >>> >>>>>packagewould be a good starting point, both a) because it is >>> >>>>> non-trivial Rails app and also b) because it is the only Rails app >>> >>>>> with a Debianpackageanyway :-) >>> >>> >>>> Hadn't seen the Redminepackage; that is a very good example >>> >>>> indeed! >>> >>>> Care to take a shot at it? I'm willing to help! >>> >>> >>>>> Isn't BlueCloth API compatible with RDiscount? I mean, it's dog- >>> >>>>> slow, >>> >>>>> but for a first approximation it should be enough. And BlueCloth >>> >>>>> is >>> >>>>> already available as `libbluecloth-ruby`. >>> >>> >>>> We extend RDiscount a little (see lib/markup_renderer.rb), but >>> >>>> creating >>> >>>> something that uses Bluecloth instead shouldn't be a biggie. >>> >>>> I'd love to see this going somewhere... >>> >>> >>> I'm really completely clueless regarding Debian packaging so far, >>> >>> but >>> >>> I did set up a couple of Gitorious instances already and would >>> >>> love to >>> >>> contribute (help with testing, qa or with packaging itself, if >>> >>> someone >>> >>> can help me to get started). >>> >>> >>> Not to turn this into a religions thing, but maybe this would be >>> >>> even >>> >>> more easy as a PPA for ubuntu (so far the most common deployment >>> >>> scenario I've seen here on this list or mentioned in installation >>> >>> tutorials), since that allows instant distribution to interested >>> >>> parties, building for multiple distribution versions etc.. >>> >>> >>> On the other hand, if the Debian base is favored: Fine for me, I'm >>> >>> interested. >>> >>> >> -- >>> >> To post to this group, send email to gitorious@googlegroups.com >>> >> To unsubscribe from this group, send email to >>> >> gitorious+unsubscr...@googlegroups.com >>> >>> > -- >>> > πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν >>> > μέγα >>> > [The fox knows many things, but the hedgehog knows one big thing.] >>> > Archilochus, Greek poet (c. 680 BC – c. 645 BC) >>> >http://wiki.hedgehogshiatus.com >>> >>> > -- >>> > To post to this group, send email to gitorious@googlegroups.com >>> > To unsubscribe from this group, send email to >>> > gitorious+unsubscr...@googlegroups.com >> >> -- >> To post to this group, send email to gitorious@googlegroups.com >> To unsubscribe from this group, send email to >> gitorious+unsubscr...@googlegroups.com >> > > -- > To post to this group, send email to gitorious@googlegroups.com > To unsubscribe from this group, send email to > gitorious+unsubscr...@googlegroups.com > -- Mike Jackson imikejackson _at_ gee-mail dot com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
