I have been thinking how we might provide binary packages for Slackware 12.2
I'm hoping that if binary packages are available, in addition to build scripts at my site, that interest will increase among Slackware users. Although many Slackers build their own packages, many do not. Yet if they can download the final packages they might spark new interest in Trinity.
I don't have the bandwidth at my meager web site to host packages.
You have offered to host packages. How do we want to do this?
If we wait until the official 3.5.12 tarballs are available, I can build those final packages. I just need to get them to you.
We would need to post and test a link at your web site just like the other links.
If we coordinated this then you could include Slackware 12.2 as part of your release announcement.
Darrell
I have been thinking how we might provide binary packages for Slackware 12.2
I'm hoping that if binary packages are available, in addition to build scripts at my site, that interest will increase among Slackware users. Although many Slackers build their own packages, many do not. Yet if they can download the final packages they might spark new interest in Trinity.
I don't have the bandwidth at my meager web site to host packages.
You have offered to host packages. How do we want to do this?
If we wait until the official 3.5.12 tarballs are available, I can build those final packages. I just need to get them to you.
We would need to post and test a link at your web site just like the other links.
If we coordinated this then you could include Slackware 12.2 as part of your release announcement.
Darrell
If you can get the packages to me at least one day before release, then I will create a Slackware folder on the main project mirror that contains them. One way to do this would be for you to temporarily publish a tarball on your website under a private link that only you and I know.
Let me know what you think!
Tim
If you can get the packages to me at least one day before release, then I will create a Slackware folder on the main project mirror that contains them. One way to do this would be for you to temporarily publish a tarball on your website under a private link that only you and I know.
Okay, let's try that.
How about prepping the folder before then so we can test? I can upload some of the smaller packages to provide a testing bed. You could create the link on the main page when ready for the official release, but we can test the back end before then.
For some reason my builds failed last night. SVN 1180441. I suspect the problem is ccache and not using make clean correctly. I wish I knew what I was doing wrong. The build seems to be going okay now, but to be sure, I will have to purge svn and update, then wait another 8 hours to prove the build succeeds.
I think rather than use ccache I'll revert to the previous method I used of copying the svn files to tmpfs. That is the same basic method you use with using rsync to create a copy of svn. I could try that too and then hope ccache works correctly on the second copy of svn, but if not, then I have a local svn copy to quickly duplicate. Copying svn to tmpfs prevents using ccache but always provides a clean directory.