----- Original Message ----- From: "Ben Reser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 14, 2002 10:11 PM Subject: Re: [Cooker] new rpm and unpackaged files
> On Thu, Nov 14, 2002 at 02:51:05PM -0500, David Walluck wrote: > > No, it's forcing the lazy developer (packager) to take an active stance. > > You sent an email complaining how no one tests packages. Well, this is a > > part of that. It forces them to not be lazy and exclude certain files > > because they just forgot to add them to the files list. > > And it creates more work for those of us who aren't lazy but might be > intentionally excluding files. > > > One drawback I see, however, is that the lazy developer will again > > become lazy and start using wildcards all over the place in the > > filelists. That's a bad idea too. > > Yup or just disabling the check by setting the macro to 0. > How about this: Since there is a switch to disable the check, why not add a switch that changes the TERMINATE mode to WARNING mode? example: if this: %define _unpackaged_files_terminate_build 0 disables the check, why not add: %define _unpackaged_files_warning_build 1 (or whatever suitable ...) to change the terminate mode to warning mode. Then all should be happy, since it would give all what they want, - Terminate Mode - Warning Mode - No Warnings or Terminate mode.. Just a thought... ;-) Thomas *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
