SCIENTIFIC-LINUX-DEVEL Archives

April 2016

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Orion Poplawski <[log in to unmask]>
Reply To:
Orion Poplawski <[log in to unmask]>
Date:
Thu, 14 Apr 2016 21:21:22 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
On 04/14/2016 07:20 PM, Steven Haigh wrote:
> On 2016-04-15 02:45, Pat Riehecky wrote:
>> Hmmmmm.....
>>
>> We use modifyrepo to inject the updateinfo data based on the packages
>> within the metadata.
>>
>> I'll see about adjusting the process there.
>
> Is there any reason modifyrepo is used instead of just createrepo? I
> understand it may take longer to do a full (re)create, but I've never
> run into this problem when I've done repos.
>
> My workflow is rather simple, but I do:
>
> #!/bin/bash
> if [ -z $1 ]; then
>      echo "Usage: $0 <reponame>"
>      exit 1
> fi
>
> createrepo --outputdir=/path/to/repo/$1/x86_64/ /path/to/repo/$1/x86_64/
>
> rsync --delete-after --progress -a /path/to/$1/ livesite:/path/to/repo/$1/
> exit 0
>
> You could optionally use the --update parameter to update an existing
> repo - which may be faster.
>

--update is certainly faster, especially as the repo grows.  I've 
shifted to that locally.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  [log in to unmask]
Boulder, CO 80301              http://www.cora.nwra.com

ATOM RSS1 RSS2