Original sources, or not

2003-09-18 Thread Matthias Urlichs
Hi, many packages seem to contain .orig.tar.gz files which may or may not be directly related to the files actually available from upstream. That is unfortunate. I think that it would make sense to add a requirement to Policy that the .orig.tar.gz file should be an unmodified copy from

Re: Original sources, or not

2003-09-18 Thread Manoj Srivastava
On Thu, 18 Sep 2003 08:01:46 +0200, Matthias Urlichs [EMAIL PROTECTED] said: Hi, many packages seem to contain .orig.tar.gz files which may or may not be directly related to the files actually available from upstream. That is unfortunate. I think that it would make sense to add a

Re: Original sources, or not

2003-09-18 Thread Matthias Urlichs
Hi, Manoj Srivastava wrote: This would be an undue burden on a number of packages. What's undue about inserting a I created the .orig.tar.gz package by calling 'make clean_all_generated_files'. sentence in the copyright / readme / whatever file? That's all I'd require. Anything else would

Re: Original sources, or not

2003-09-18 Thread Manoj Srivastava
On Thu, 18 Sep 2003 18:25:37 +1000, Glenn McGrath [EMAIL PROTECTED] said: On Thu, 18 Sep 2003 02:01:25 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: Pristine sources are already a desired, but not required, characteristic. There are enough brain dead upstream packaging practices that we

Re: Original sources, or not

2003-09-18 Thread Matthias Urlichs
Hi, Manoj Srivastava wrote: While I admit that pristine sources are a good thing (which is  why not having pristine sources is deprecated); it is way premature  to suggest making  that a policy requirement. You might have misunderstood me. I advocate requiring either - package pristine

Policy-problem: Split package with libraries or not?

2003-09-18 Thread Thomas -Balu- Walter
I've asked the following on debian-mentors already, but didn't get an answer yet. So I am asking the experts which I expect to be on this list :): I'm stuck... As I have written some days before I am trying to package camsource - a camserv like webcam-streaming software. As usual ;) I did not

Re: Original sources, or not

2003-09-18 Thread Roland Mas
Glenn McGrath, 2003-09-18 10:30:18 +0200 : On Thu, 18 Sep 2003 02:01:25 -0500 Manoj Srivastava [EMAIL PROTECTED] wrote: Pristine sources are already a desired, but not required, characteristic. There are enough brain dead upstream packaging practices that we can not mandate pristine

Re: Original sources, or not

2003-09-18 Thread Bob Hilliard
Matthias Urlichs [EMAIL PROTECTED] writes: Hi, many packages seem to contain .orig.tar.gz files which may or may not be directly related to the files actually available from upstream. That is unfortunate. I think that it would make sense to add a requirement to Policy that the

Re: Original sources, or not

2003-09-18 Thread Manoj Srivastava
On Thu, 18 Sep 2003 11:16:49 +0200, Matthias Urlichs [EMAIL PROTECTED] said: Manoj Srivastava wrote: This would be an undue burden on a number of packages. What's undue about inserting a I created the .orig.tar.gz package by calling 'make clean_all_generated_files'. sentence in the

Re: Original sources, or not

2003-09-18 Thread Manoj Srivastava
On Thu, 18 Sep 2003 11:40:12 +0200, Matthias Urlichs [EMAIL PROTECTED] said: Manoj Srivastava wrote: While I admit that pristine sources are a good thing (which is  why not having pristine sources is deprecated); it is way premature  to suggest making  that a policy requirement. You might