Bug#491723: Status.net Debian Package
Hi again,
On 23/09/10 14:28, Leo 'costela' Antunes wrote:
>> Can we work together on this?
>
> Sure! Absolutely!
> Starting next week I'll take a look at the git.d.o code and see if I can
> help out with anything. I'll also be around #statusnet.
After some delays, I've finally managed to sit down and work on the
package. I have a very preliminary, though apparently
fully-functional[0] version up here[1].
I also took the liberty of starting a new git-repo, currently here[2],
just because I wanted a better notion of what had to be done (I did
however take a lot of the files from the old repo). If you're ok with
it, I'd replace the one currently in collab-maint with mine and we can
all keep working together from there.
There are still a couple of open questions:
- how much automatization do we want with the configuration? I
personally think the current level isn't that bad, that is: a single
"a2ensite statusnet.conf" (in case of apache) is enough to have an
instance working on localhost. I still haven't tested this with lighttpd
though...
- debian/copyright needs a big overhaul before any official upload
(that's a boring part I didn't have enough willpower to tackle til now)
- all libs in extlib which aren't currently separately packaged have
been included in the binary. I don't think this is particularly bad, but
the ftp-masters will obviously have the final word. Worst case scenario
I could try packaging them all individually.
- I'm unfortunately only very superficially familiar with statusnet, so
I need some help sorting out what to do with all the scripts and
pseudo-daemons in the package. Which of them do you think would be worth
having work out-of-the box? (maildaemon, for instance, is something I
think would probably be too hard to get right)
I'd really appreciate some comments and tests.
Cheers
[0] haven't tested the plugins yet
[1] http://people.debian.org/~costela/packages/
[2] git://git.debian.org/~costela/statusnet.git
--
Leo "costela" Antunes
[insert a witty retort here]
Reply to: