[ Roger Meier ] > From my perspective, the easiest way to maintain debian packaging > would be the Thrift subversion repository itself. > > Issues can easily be addressed via JIRA and Packages can be made > available on the Thrift website directly as long as they are not > within official Debian releases. > > What are your thought's?
There are so many reasons this is not a good idea; I'm not really sure where to begin. For starters, I don't have access to Thrift's subversion repository and patch submission would seriously inhibit my worflow. Likewise other Debian Developers don't have access to Thrift's repo, while they do have access to the collab-maint repo on git.debian.org. It's one thing to impede my work, but impeding the work of others in the Debian community means I will likely not get their help. Even if access weren't a problem, colocating the packaging source in the same VCS is still not an option because Debian package releases do not, and should not occur in lockstep with Thrift releases. Secondly, this bug report is for including Thrift in Debian. It's best to think of this as more of an aggregate work created from the upstream Apache project. Debian users are going to submit bugs to the Debian BTS not JIRA, some of these will no doubt pertain to Thrift itself, but many of them will pertain to the packaging and integration in Debian, and have nothing to do with Thrift. -- Eric Evans eev...@debian.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100826173459.ga32...@erebus.lan
