You could also generate a timestamp by means of the "date" command,
and use AC_SUBST for substituting the PSTAMP placeholder with the
althus generated timestamp. I would suggest writing the output of this
"date" command to a file so we can make the generation of the package
depend on that timestamp.
Best regards,
Olivier
----- Original Message -----
From: Jeff Morriss
|
| Doing a "pkginfo -l ethereal" shows:
|
| > PKGINST: ethereal
| > NAME: ethereal 0.10.5
| > CATEGORY: application,network
| > ARCH: sparc
| > VERSION: 0.10.5
| > VENDOR: Ethereal Development Team
| > DESC: A GUI network protocol analyzer
| > PSTAMP: 2000-07-16
| > INSTDATE: Jul 12 2004 17:17
| > EMAIL: gerald@xxxxxxxxxxxx
| > STATUS: completely installed
| > FILES: 95 installed pathnames
| > 5 shared pathnames
| > 13 directories
| > 49 executables
| > 58134 blocks used (approx)
|
| Note the PSTAMP from 4 years ago...
|
| Simply removing the PSTAMP line (from "pkginfo.in"):
|
| > Index: packaging/svr4/pkginfo.in
| >
===================================================================
| > --- packaging/svr4/pkginfo.in (revision 11736)
| > +++ packaging/svr4/pkginfo.in (working copy)
| > @@ -6,7 +6,6 @@
| > CATEGORY="application,network"
| > DESC="A GUI network protocol analyzer"
| > VENDOR="Ethereal Development Team"
| > -PSTAMP="2000-07-16"
| > EMAIL="gerald@xxxxxxxxxxxx"
| > ISTATES="S s 1 2 3"
| > RSTATES="S s 1 2 3"
|
| makes the package creation process add a (current) timestamp,
something
| like:
|
| > PSTAMP: beartooth20040330110147
|
| (though it will generate a warning message when the package is
| created--I'm not sure why as I think this is the best way for
PSTAMPs to
| be created.)
|
| _______________________________________________
| Ethereal-dev mailing list
| Ethereal-dev@xxxxxxxxxxxx
| http://www.ethereal.com/mailman/listinfo/ethereal-dev
|
