Bug#524135: Maintenance
Ok, I see your doubts and I'm happy to discuss these things here in detail.
So we hopefully would be able to come to the best solution for all
involved sides:
- the Thrift project and its community itself
- Thrift users
- Debian (and other GNU/Linux Distributions or deployment formats like
maven).
Let me explain my situation and probably that one others have as well.
I would like to deploy Thrift for a few globally distributed development
teams.
e.g. C++ on Debian (currently Lenny), C# on Windows, Java, etc.
I really want to deploy well defined official version, no local
repositories and patches.
=> only if there is a strong requirement
So I would need the possibility to add a
/etc/apt/sources.list.d/thrift.list file with defined versions.
pinning seems too be much overhead to do that each machine...
ok, there is the possibiliy to create a local mirror....but that's work;-)
or would it be easier to change to select the versions via pinning
instead of changing the sources.list ?
however, I get to the point...
I would like to have every thrift version available as debian package
and the possibility to select to required
version easily for lots of development machines, where people are not
very familiar with Debian or Thrift.
They should just use these Tools and code their stuff in C++, Java,
whatever.
--roger
Am 26.08.2010 19:34, schrieb Eric Evans:
[ 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.
Reply to: