+1semi wrote:0.74b3 could be installed to debian like this:Will you guys who made current .debs please talk to Tobi and upload the packages to his apt repository, so while you are in the process of solving the problem in the long run, people who are already using the previous debs could upgrade easily today?Code: Select all
echo "deb http://www.osrts.info/~tvo/deb etch spring" >> /etc/apt/sources.list aptitude update aptitude install spring spring-data
I'm willing to take over the Ubuntu Spring packages
Moderator: Moderators
Exactly. Ubuntu and Debian will not release updates to already released versions. The best we can hope for is that it'll be a long while between Spring releases and that the current distribution will have the current package (or it'll creep in through backports). We'll need our own repository anyway - in fact this is very similar to what happens with Wine, which has even more frequent releases than Spring.CautionToTheWind wrote:The problem with official packages is update frequency. Being a version behind just won't cut it when the master server refuses the connection.
In my opinion the existing debs are very close to a perfect solution. If we could get our own repository, so that i dont even have to manually download the debs, that would be perfect. Later we could put a linux lobby in those repos too.
Agreed, I'll start hunting him down. If I can get trusted to run the machine, it'll be pretty much the same as the winehq APT repository.semi wrote:Will you guys who made current .debs please talk to Tobi and upload the packages to his apt repository, so while you are in the process of solving the problem in the long run, people who are already using the previous debs could upgrade easily today?
I could even maintain edgy and etch forks like I do for Wine.
- Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18