Re: Must I compile a palm-program to include in deb?
On Wed, 13 Dec 2000, Brian Almeida wrote:
> On Wed, Dec 13, 2000 at 08:49:07AM -0800, Sean 'Shaleh' Perry wrote:
> > > I'd like to use the provided viewer.prc. I think it's ok, because
> > > it's not supposed to run on debian. By the way, is there a policy
> > > that everything must be built from sources in debian? I guess it
> > > should be, but I havent found it.
> >
> > apt-get install debian-policy packaging-manual
> > cd /usr/share/doc/debian-policy # or packaging-manual
> > read files
> >
> > quick summation: every package in Debian must be buildable within Debian.
> > Otherwise it is non-free (binary only). prc files may be an exception -- they
> > could reasonably be treated as data. However, if your package in main contains
> > a non-free palm package, I would be loath to consider your package free.
> Plucker is GPL, but requires prc-tools to build the source... the version
> of prc-tools in debian is woefully outdated, but the new upstream (2.0)
> requires an SDK from palm to compile, which is most DEFINATELY non-free...
> you have to sign up for their 'developer's pavilion' to even download it.
> So the .prc itself is free, but the development environment is really not.
> For more info on plucker, see http://plucker.gnu-designs.com
Ugh, still the development tools are really outside the scope of the
license. My gut feeling is to include source and binary, and don't bother
with compiling it during package build. I know it sucks... Anyone else
have any better ideas?
Oh, and for precedent re: debian packages that require files outside of
debian to build, see gcc-m68k-linux. That package has been bothering me
for YEARS. Has to do with libc headers that aparantly cannot be placed
where the package requires them.
Reply to: