Conversation
Notices
-
@bes One example can be taken from when @bob has packaged !GNUsocial for Debian. I prefer to have everything packed into the same repository - just one git pull (no remote dependencies that when failing will break the build). While Debian wants to split everything into their individual packages, so they can be updated individually.
I personally wouldn't be able to keep up with tracking multiple different versions in various distributions. So more workpower is needed. And at least for me, it's pretty boring, tedious work that I don't want to do as a developer :)
(which is why I think @bob is awesome, putting a lot of time into identifying individual packages etc.)-
@mmn It's of course much better to have separate packaging ("severe bug in PEAR::DB? then just update that package and everyone benefits!", but it's still pretty cumbersome :])
Some of these things have been suggested to be solved in !GNUsocial with using composer for PHP, but given that I have no experience (nor is there a package for composer in Debian Jessie, which is what I use) I prefer to just stick with the old ways until someone else does all the work. #lazy #asshole
-
