Re: new fields in debian/control
>>"Clint" == Clint Adams <schizo@debian.org> writes:
>> I could definately see where you do 'dpkg-buildpackage -O debian' or
>> 'dpkg-buildpackage -O corel'
Clint> What? Why would anyone want a proliferation of packages that
Clint> are identical except for one control field? If Plagiarism
Clint> GNU+Linux wants to take my package, modify nothing except the
Clint> control file, what purpose does it serve to have bug reports
Clint> go to them instead of to me? In fact, what purpose does it
Clint> serve to even have the duplicate package at all?
This is a very narrow view. I often have local packages, I try
them out as experiments, and may well have different policies, build
depends, etc for when they are local, as opposed to when they are
uploaded by me to Debian.
If tweaking the design allows this wider usage, why should
we not do iut that way? ANd, incindetllay, I think one should have
origins be handled the same way dupload handles upload locations:
each origin could have its own preset BTS field, etc, and as long as
I am happy witht he defaults, I can switch from local + tested to
debian upload with no changes.
manoj
--
What does "it" mean in the sentence "What time is it?"?
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: