apt/ rpm package support

[nicolai86]

To ease the installation of sqitch it would be great to have a package for apt/ rpm and possibly also a homebrew formula.

I'd be more than happy to help with this even tho I've no experience building apt packages. Any ideas/ feedback on what would be necessary would be great.

As for the process I thought it'd be great to test the packages on a number of OSses, preferebly by some kind of configuration tool like ansible.

[theory]

I have done all the work to build RPMs on CentOS 6, and would be happy to contribute the requisite spec files. Anyone got an entrée to EPEL to submit them?

[rajivr]

@theory Can you gist the spec files in the meantime? That would be really helpful.

[theory]

Yes, I'll try to get that done this week.

[theory]

Done.

[rajivr]

Thank you @theory. I am wondering if you have a SPEC file for sqitch package as well?

[theory]

Yep, it's right here.

[acrobat]

an apt package would be great!

[theory]

FYI, I am replacing Mouse and Moose with Moo. I removed the Spec files for Mouse and Moose in 70f7fba and added Moo and Type::Tiny and dependencies in b1b2644.

[theory]

Just found this. So does that mean that Sqitch is available on Debian and its derivatives now?

[andrewalker]

Yay, awesome news :) Although...

dep: libmoose-perl modern Perl object system framework

dep: libmouse-perl (>= 1.04) lightweight object framework for Perl

Shouldn't be necessary in recent versions, right? So a load of other deps could also be dropped, I suppose.

[theory]

Yes, that’s correct. In email I'm told that the number of dependencies for Amazon Linux dropped from 63 to 22!

[acrobat]

The only issue with this is that the package is only available in debian sid channel (unstable channel) so it's not recommended to use it for production servers..

[theory]

@acrobat Will it eventually end up in stable? Is testing > unstable or < unstable?

[acrobat]

@theory my guess would be, when a stable version of sqitch is released the maintainer of the debian package of sqitch will push that version to the testing branch and when it's passed through the cycle it will eventually be available on the stable repository. But i don't how long that will take (maybe the current maintainer can give some info on that). This is the life cycle "unstable → testing → stable"

But about using sid is the faq very clear

Should I use sid on my server? Are you insane? No!

Should I use sid on my desktop? If you think you can handle a broken Debian system, sure. Do you know what to do if libpam0g breaks, preventing all logins? Do you know what to do if grep breaks, causing the boot process to hang forever? These things have happened. They will happen again.

If you'd like to avoid the brown-paper-bag bugs like these, then use testing instead.

[theory]

Yeah, but Debian has always been extremely conservative. I never used stable myself, because it was always way too old.

[acrobat]

I know, for personal use, i also never used debian stable. But the way they keep there stable is just ideal if you host a server and want a stable system, without having to worry about package updates that could potentially break your app's on that server. If you need a newer version of a package you can still use the backports repository or use a custom repo (like for example dotdeb)

[ylavoie]

Any news on this? Would you consider Ubuntu instead or Debian?

[theory]

I have no objection to anyone creating a distribution package on any platform. I welcome it! But I personally don't have the TUITs for it beyond providing what limited tools I've made for the CentOS environments we have at $work. Can you create an apt package for Ubuntu, @ylavoie?

[rpkamp]

It seems sqitch is already in Ubuntu: https://launchpad.net/ubuntu/+source/sqitch

[theory]

@rpkamp Nice, though it looks like they don't have v0.9996 yet.

[theory]

FIWW, there's now a Docker image; see thedocker-sqitch project for details.