Dagobert Michelsen <[email protected]> writes: > Hi, > > Am 21.02.2013 um 10:24 schrieb Maciej (Matchek) Bliziński > <[email protected]>: >>> Finally, when I'm writing "luxury" I think to what was suggested by Dag, >>> i.e. when using only the "packaging" target on a system which has >>> checkpkg activated showing what should be the checkpkg stanza; and this >>> is not a luxury but a necessity as we have seen. >> >> Some GAR code refactoring will be required around line 1015 of >> gar.pkg.mk, so that you can either run or display the checkpkg >> command, and you still keep all how-to-run-checkpkg information in one place. >> >> Dago, is it doable? > > The question is what the workflow would be and what should be done. A good > thing would IMHO be > > - mgar package > - (Edit some stuff) > - mgar repackage-CSWjustone > > After the individual repackage all packages would be checked together. > Checking just one > package would IMHO be too dangerous. Additionally, I would remove the target > package-CSWfoo > as it indicates it could be explicitly called. Building just one package > without the others > first is also a usecase I would like to avoid. > > Peter, would this be acceptable?
In principle yes. However, for cas-* packages the work-flow is: - package one cas - upload the resulting cas which is usually architecture neutral -- Peter _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
