On 15/01/14 21:45, Jan Rękorajski wrote:
My proposal is to do what Fedora does in its repo, for a retired package:
1) git delete all files in package, spec, patches, etc.
2) create "dead.package" file with explanation why it was retired (for
example "Obsoleted by XXX" or "Renamed to YYY")
3) make package read-only to avoid grave digging
this would apply only packages that "Were on ftp"?
we still have packages which are duplicates and need merging to one
package, "retiring" before merge does not seem right.
what about packages that provide alternative versions, for example
ruby.spec provides ruby-json 1.5, but ruby-json provides newer version
that some ruby packages already require. similar situation exists with
perl modules bundled from perl.spec.
also, qboosh has just noted in spec comments that it's obsolete,
probably to be able to build old versions (enlightment packages)
also, should github mirror delete retired packages?
--
glen
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
