mrevilgnome 2013-03-29, 21:01
Jonathan Creasy 2013-03-29, 21:25
Manish Bhatt 2013-03-29, 22:42
BTW, here is how one guy did it. He rebuilds the upstream tarball after the
build so there is no discrepancy for the debian build packaging scripts.
On Fri, Mar 29, 2013 at 3:41 PM, Manish Bhatt <[EMAIL PROTECTED]> wrote:
> We are trying that right now for Debian and finding that the current
> version makes it nearly impossible to follow packaging best practices.
> 1) The build process does not allow specification of a target directory,
> and thus pollutes the upstream package.
> 2) The build process downloads packages during build time, which breaks
> exact reproducibility.
> 3) It comes bundled with and relies upon packages, such as scala, instead
> of looking for a separately installed scala package.
> We can't devote too much engineering time so for now our solution
> preserves a clean upstream by cleaning out the pollution from (1) after the
> build so that debian does not complain), we live with (2), and are writing
> our own helper scripts to set the classpath for things like (3).
> I'm sure there are many reasons/history for 1-3, including Kafka's nascent
> version number (less than 1.0). Overall I'm grateful that Kafka is provided
> as open source.
> On Fri, Mar 29, 2013 at 2:01 PM, mrevilgnome <[EMAIL PROTECTED]>wrote:
>> Has anyone gone through the effort of packaging Kafka for Ubuntu, Debian,
>> or CentOS? I'm partially through the process for Ubuntu, and I figured I
>> should ask. Thanks.
mrevilgnome 2013-04-01, 04:28