On Tue, 8 Dec 2009, Allison Randal wrote:
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.
Ok, I've marked the ticket as WONTFIX due to differences in packaging
philosophy. These differences in packaging philosophy have been discussed
before, so probably don't need to be discussed again, but I've summarised them
briefly in the ticket for those interested. It was lack of realisation about
how Allison's packaging philosophy applied that made me submit the ticket in
the first place.
HTH,
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [email protected] | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
