Am Dienstag, den 15.05.2007, 19:20 +0200 schrieb Michael Schwendt:
> On Tue, 15 May 2007 19:15:07 +0200, Thorsten Leemhuis wrote:
>
> >
> > >>>> Author: ajax
> > >>>> + mkdir -p ${DESTDIR}${MANDIR}
> > >>>> + cp powertop.1 ${DESTDIR}${MANDIR}
> > >>> cp -p would keep timestamps. Maybe not worth it if powertop.1 is
> > >>> generated, I haven't checked...
> > >> It isn't. Why would I care about timestamp?
> > > Packaging guidelines state that it is preferrable to keep timestamps on
> > > installed files the same as what was packaged.
> >
> > Well, to give a better reasons than "because it's written": for multilib
> > installs it's important that the timestamps are identical for files that
> > are in both the i386 and x86_64 packages.
> >
> > And (in the long term) making sure the timestamp didn't get changed
> > might make things easier for presto as well.
>
> For documentation files and scripts -- and files in general ;) -- it is
> nice to know when a file is several years old. For %config files it is
> great when mtime only changes when a file is updated actually.
>
+1
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
