On Fri, 2017-01-13 at 03:00 +0100, Albert van der Horst wrote: > [Sorry for the long quote]
Sorry for the delay :) > The generic system for ciforth is now present in github. > https://github.com/albertvanderhorst/ciforth Great :) > This is a complete copy of the rcs/cvs system with all versions, > logs and tags since 2000. Nice. I noticed the CVS tags don't seem to have been converted to git tags. How do you intend to modify the ssort binary if you need to? The README.ciforth file says "Contact me if you want source." and looking at the `strings ssort` output it seems like the source for ssort is a C++ file called ssort.cc. I would suggest removing the ssort binary from your git repository. You could then either commit the ssort.cc file and a Makefile update to the ciforth repository, or you could convert any existing ssort repository to git and then publish it. If you chose the latter option then the ssort github repository would need to be mentioned in README.ciforth, ssort would need to be packaged for Debian as well as ciforth and the ssort package would then become a build dependency of ciforth. On one hand ssort is a small program that probably isn't used by any other software than ciforth so merging it into ciforth should be fine. On the other hand ssort is a generic utility so it might be or become useful outside the ciforth project. > The latest releases for up to eight targets are in the subdirectory > release. Relevant for Debian are the 32 and 64 bit linux versions. I think it might be better for you to create github tags/releases and then attach the prebuilt binaries to those tags via the web interface, instead of committing generated files and tarballs to the git repo. In addition, Debian will want to build the executables on our buildds rather than using the pre-built versions. This is so that we know we can guarantee to our users that they can also build from scratch and then modify and rebuild as they need to. > I would be happy to find a sponsor for lina32, which is a runtime > package without dependancies. Building the package requires pdftex, > texinfo and gas. The way it would work is that you would create a ciforth source package, containing the output of `git archive` which github produces and then that source package would contain a debian/ directory listing the binary packages it produces and instructions on how to run the upstream build system to build and install the right files. > I'm willing to invest in understanding the making of deb files > and maybe add that to the generic system. Please start by reading through this: https://mentors.debian.net/intro-maintainers -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
