#873: Blanket ports exclusion needs discussion
----------------------+-----------------------------------------------------
Reporter: wayland | Type: RFC
Status: closed | Priority: normal
Milestone: | Component: install
Version: 1.4.0 | Severity: medium
Resolution: wontfix | Keywords:
Lang: | Patch: new
Platform: linux |
----------------------+-----------------------------------------------------
Changes (by wayland):
* status: new => closed
* resolution: => wontfix
Comment:
Due to a difference in philosophy about how a tarball should be turned
into an RPM, Allison has rejected this patch. Allison's opinion (quoted
from an e-mail; hopefully not too much out of context):
----
"The ports directory shouldn't be included in the tarball. It's just
storage for the spec files
from various distributions. That is, when various distributions create
packaging scripts, etc,
we ask them if we can store a copy of those files back in the Parrot repo.
It's good safety in
case one of the distro package maintainers disappears and someone else
needs to pick it up
(which has happened before)."
"But, packagers do their work after the release, and it's common to make
an updated package from the same tarball if distro patches need to be
added. So old spec files included in the tarball are generally wrong, and
just clutter the packager has to write over".
----
My philosophy (and that of some others, I think), on the other hand, is to
have one RPM spec file that works everywhere, and with the current
release, and to prepare it with the release. This philosophy has been
rejected in earlier tickets, but I have trouble keeping Allison's
philosophy in my head. But I agree that since Allison is the core
developer, and I'm just a drop-in, Allison's opinion takes precedence over
mine (not sure about others). I hope this doesn't come across as upset or
anything; perpetually confused, maybe, though :).
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/873#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
