Hi guys, On Mon, Jun 29, 2015 at 03:29:51PM +0200, Johannes Schauer wrote:
> As for the second problem (the empty Packages file) I was annoyed by this > myself for a long time and would like to get to know a use case where an empty > input file would make sense. Currently I'm working around this by > conditionally > only running dose3 in my scripts when the input is not empty but I'd like to > get rid of these checks. So I'm curious: what is your use case to use an empty > Packages file? A possible use case for having one empty input file (along with some others that are not empty) is that a file is generated by a script. For instance, you might have as background all the packages in your distribution, and a script that creates pseudo-packages implementing that you want to have certain packages installed thogether while some others are required to be not installed. Cheers -Ralf. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
