Re: RPM %files installation directory confusion

From: Rose (spamaccout69_at_yahoo.com)
Date: 10/28/03

  • Next message: Gina: "Function to read the superblock"
    Date: 28 Oct 2003 14:33:10 -0800
    
    

    Ok so now I have a spec file that looks like this ( I am not doing a
    build of the binaries or the install just package up in an rpm)
    BuildRoot:/var/pbiace/rel_2003_10

    %build

    %install

    %files

    /bin/*
    /cdunix/*
    /cfg/*
    /lib/*
    /ndm/*
    /transfer/*

    and the error is File not found by glob: /var/pbiace/rel_2003_10/bin/*
    (for each one)
    /var/pbiace/rel_2003_10 is the installation target directory not the
    pick up area. I have moved the binaries to the %_topdir/BUILD
    directory in the /var/pbiace/rel_2003_10 directories.

    here is the output from the build:

    + umask 022
    + cd /export/home/ca6459/ccm_wa/ace/ace#ca6459_2003_09/ace/test2/deploy/BUILD
    + exit 0
    + umask 022
    + cd /export/home/ca6459/ccm_wa/ace/ace#ca6459_2003_09/ace/test2/deploy/BUILD
    + exit 0
    File not found by glob: /var/pbiace/rel_2003_10/BuildofMaterials.*
    File not found by glob: /var/pbiace/rel_2003_10/bin/*
    File not found by glob: /var/pbiace/rel_2003_10/cdunix/*
    File not found by glob: /var/pbiace/rel_2003_10/cfg/*
    File not found by glob: /var/pbiace/rel_2003_10/crontab/nodataman.*
    File not found by glob: /var/pbiace/rel_2003_10/lib/*
    File not found by glob: /var/pbiace/rel_2003_10/ndm/*
    File not found by glob: /var/pbiace/rel_2003_10/transfer/*

    Markku Kolkka <markku.kolkka@iki.fi> wrote in message news:<bnb063$slj$1@phys-news1.kolumbus.fi>...
    > Rose wrote:
    > > In my spec file in the %files section I have defined where to pick up
    > > and which files to pick up....for example:
    > > /export/home/myhomedir/workingarea
    > > then when I install it trys to put the binaries back in the same
    > > location. I want them to install to /var/lib/applicationname.
    >
    > Define your BuildRoot as "/export/home/myhomedir/workingarea", copy the
    > files in the %install section to
    > $RPM_BUILD_ROOT/var/lib/applicationname, and in the %files section list
    > the files to be packaged without the prefix
    > (/var/lib/applicationname/*)
    >
    > http://www.rpm.org/max-rpm/ch-rpm-anywhere.html


  • Next message: Gina: "Function to read the superblock"

    Relevant Pages

    • RE: Package bundling guidance
      ... exit with a successfull exit code so you can go on... ... In your package "My Package" say you have 3 programs listed. ... check "Run another program First" ... Install the new version ...
      (microsoft.public.sms.swdist)
    • Re: Package bundling guidance
      ... Windows Server System MVP - SMS ... exit with a successfull exit code so you can go on... ... In your package "My Package" say you have 3 programs listed. ... How are you checking to see if the previous version was install, ...
      (microsoft.public.sms.swdist)
    • Re: Package bundling guidance
      ... exit with a successfull exit code so you can go on... ... In your package "My Package" say you have 3 programs listed. ... I have a situathion where we need to upgrade Interwise from V6.52 to ... Install the new version ...
      (microsoft.public.sms.swdist)
    • Re: TeX Live, Fedora and tlmgr
      ... doesn't update binaries between releases. ... What TeXLive would bring me is a package manager. ... Once I am done with my present workload, I do intend seeing if there is anything I can do to help the Deb people upgrade everything to TL2011, but it will probably be TL2012 by the time I am free. ... The later can be needed if one wants to install auctex afterwards ...
      (comp.text.tex)
    • Re: installing mod_ssl on Fedora Core 4 -- complaining about httpd =?UTF-8?B?PQ==?= 2.0.
      ... just used the standard httpd binaries, which would have enabled me to ... Rather than giving you a stock Fedora server to play with, they stuff with some frankenpackages. ... Then, once that package is nuked from high orbit, I'd compile a list of all the little packages that make up that php frankenpackage, then I'd run ... After they're gone, I'd just run "yum install", which should now pull in the standard Fedora version of these packages. ...
      (comp.os.linux.misc)