Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: "Siders, Keith" <keith_siders@toshibatv.com>
Cc: "Linux-Mips (E-mail)" <linux-mips@oss.sgi.com>
Subject: Re: general linux question
Date: Wed, 2 Jan 2002 21:41:10 +0100	[thread overview]
Message-ID: <20020102204110.GA5075@paradigm.rfc822.org> (raw)
In-Reply-To: <7DF7BFDC95ECD411B4010090278A44CA1B74D9@ATVX>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

On Wed, Jan 02, 2002 at 11:36:27AM -0600, Siders, Keith wrote:
> This isn't mips-specific, so maybe belongs on another list, but I figured
> someone here could probably answer just as quickly. I need to track versions
> of all files in the system (embedded, flash-based, no disk media), but
> cannot find a structure member where a version number can be stored in a
> file header. Most linux command line apps generally have a -version command
> line option, but is not viable for our application. Have I missed something?
> Is there a standard Linux method/practice for version number tracking and
> retrieval that is separate from CVS and the -version command switch, or do I
> have to use something proprietary? Or should I just try to use the file
> creation timestamp?

Usually this is the reason for a distribution which stores some kind
of metadata in some flavour of package database:

(flo@paradigm)~# dpkg -l gcc binutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  gcc            2.95.4-9       The GNU C compiler.
ii  binutils       2.11.92.0.12.3 The GNU assembler, linker and binary utiliti


Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
Nine nineth on september the 9th              Welcome to the new billenium

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-01-02 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 17:36 general linux question Siders, Keith
2002-01-02 17:52 ` Bradley D. LaRonde
2002-01-02 20:30 ` Marc Karasek
2002-01-02 20:41 ` Florian Lohoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-02 18:21 Siders, Keith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020102204110.GA5075@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=keith_siders@toshibatv.com \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox