- it cannot handle epochs
- a lot of my packages' upstream seems to have gone or moved
- some of my packages are native packages, but they are not directly related to debian. I think this was just because the previous maintainer (like me) was part of the upstream team and disliked the additional problems caused by a non-native package. This is starting to bite however and when I try to reverse the situation I often see that the debian version is higher then the last official release of that project. So I need to use epochs. See point 1 :-(.
So my big plan to have all my packages in darcs and attracting a multitude of helpers seems to have fallen foul. I will still try to get this into some shape and make it available...
sbcl has run into some gcc-4 problem on some platforms and cmucl won't even build using gcc-4. A lot of work needs to be done and there is so little time, mostly because of the evil daen free library that is sucking away hours like a baby milk.
1 comment:
Just to be clear -- the epochs problem is with darcs-buildpackage (so you can blame me), not with darcs itself. darcs-buildpackage is a collection of wrappers around darcs to automate using it with Debian packages.
Post a Comment