Re: can a non-buildable part remain in source

2004-03-10 Thread Matthew Palmer
On Wed, Mar 10, 2004 at 07:38:45AM +, Thomas Viehmann wrote: > Matthew Palmer ([EMAIL PROTECTED]) wrote: > >On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: > >> I have a package that has an optional part that cannot presently be > >> built in main but ships a (java bytecode) bi

Re: can a non-buildable part remain in source

2004-03-10 Thread Thomas Viehmann
Matthew Palmer ([EMAIL PROTECTED]) wrote: > >On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: >> I have a package that has an optional part that cannot presently be >> built in main but ships a (java bytecode) binary in the tarball. >> Policy prevents me from adding this to the bina

Re: can a non-buildable part remain in source

2004-03-10 Thread Matthew Palmer
On Wed, Mar 10, 2004 at 07:38:45AM +, Thomas Viehmann wrote: > Matthew Palmer ([EMAIL PROTECTED]) wrote: > >On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: > >> I have a package that has an optional part that cannot presently be > >> built in main but ships a (java bytecode) bi

Re: can a non-buildable part remain in source

2004-03-09 Thread Thomas Viehmann
Matthew Palmer ([EMAIL PROTECTED]) wrote: > >On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: >> I have a package that has an optional part that cannot presently be >> built in main but ships a (java bytecode) binary in the tarball. >> Policy prevents me from adding this to the bina

Re: can a non-buildable part remain in source

2004-03-09 Thread Matthew Palmer
On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: > I have a package that has an optional part that cannot presently be > built in main but ships a (java bytecode) binary in the tarball. > Policy prevents me from adding this to the binary debs, but my > understanding of policy is tha

Re: can a non-buildable part remain in source

2004-03-09 Thread Matthew Palmer
On Tue, Mar 09, 2004 at 05:32:03PM +0100, Thomas Viehmann wrote: > I have a package that has an optional part that cannot presently be > built in main but ships a (java bytecode) binary in the tarball. > Policy prevents me from adding this to the binary debs, but my > understanding of policy is tha

can a non-buildable part remain in source

2004-03-09 Thread Thomas Viehmann
Hi. I have a package that has an optional part that cannot presently be built in main but ships a (java bytecode) binary in the tarball. Policy prevents me from adding this to the binary debs, but my understanding of policy is that I can keep it in the orig.tar.gz for the sake of using an unchange

can a non-buildable part remain in source

2004-03-09 Thread Thomas Viehmann
Hi. I have a package that has an optional part that cannot presently be built in main but ships a (java bytecode) binary in the tarball. Policy prevents me from adding this to the binary debs, but my understanding of policy is that I can keep it in the orig.tar.gz for the sake of using an unchange