Re: future Date: field for Packages files
Dan Jacobson [EMAIL PROTECTED] writes: Regarding a future Date: field for each package in Packages files, * Should the field be called Date: or Time:? * Should it be like Mon, 18 Aug 2003 22:09:30 GMT or 1061315862? * Should it refer to the time the developer finished wrapping the package, or the time it entered the distribution? Those questions are for you implementers to decide. I merely look forward the day when one can tell apt-show-versions --upgradeable, or grep-available, that one is only interested in versions that have been around for more (or less) than X days. It shouldn't be changed after its signed, or will this not be included in the deb too? MfG Goswin
future Date: field for Packages files
Regarding a future Date: field for each package in Packages files, * Should the field be called Date: or Time:? * Should it be like Mon, 18 Aug 2003 22:09:30 GMT or 1061315862? * Should it refer to the time the developer finished wrapping the package, or the time it entered the distribution? Those questions are for you implementers to decide. I merely look forward the day when one can tell apt-show-versions --upgradeable, or grep-available, that one is only interested in versions that have been around for more (or less) than X days.
Re: future Date: field for Packages files
On Wed, 20 Aug 2003, Dan Jacobson wrote: Regarding a future Date: field for each package in Packages files, * Should the field be called Date: or Time:? * Should it be like Mon, 18 Aug 2003 22:09:30 GMT or 1061315862? * Should it refer to the time the developer finished wrapping the package, or the time it entered the distribution? Those questions are for you implementers to decide. I merely look forward the day when one can tell apt-show-versions --upgradeable, or grep-available, that one is only interested in versions that have been around for more (or less) than X days. We had made a descision on this? I certainly hadn't.
