On Mon, Apr 12, 2010 at 09:11:54AM -0400, rhurst@bidmc.harvard.edu wrote: > If you do not want to provide RPM packages, that should not prevent them > from getting created and pushed upstream to another repository. If you want > to maintain an rpm SPEC file (for inclusion of new source and header files, > etc.), that would be grand (for me). :) It's not that I don't want to provide the packages, but I assume that this is no longer necessary if they're part of an official repository. Let's see how this works out. > I have setup subversion to keep a source copy of your releases only (trunk > and tags) from which to build the RPM source and binary packages. My nightly build script does an automatic checkout and builds all packages including RPMs (provided that the platform is RPM based which is no longer the case with my main work station). If you're interested, I can check if it is possible to strip it down for your use. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon Apr 12 17:07:37 2010
This archive was generated by hypermail 2.1.8 : 2010-04-12 17:07:40 CEST