[Bug 468189] Review Request: rear - Relax and Recovery (disaster recovery framework)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=468189


Gratien D'haese <gratien.dhaese at it3.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?(gratien.dhaese at it |
                   |3.be)                       |




--- Comment #25 from Gratien D'haese <gratien.dhaese at it3.be>  2009-02-13 10:58:46 EDT ---
Hi all,
thank you (Robert) for taking a closer look into rear - much appreciated - the
goal is indeed to make the software cleaner (and better).

As Schlomo (in #24) already mentioned the doc files are kept double for the
simple reason that it is very easy to make a new 'in-house' rpm for example
(with the command 'rear mkrpm'). However, if we must exclude them, we can of
course. In that case the customers who want to build their own in-house rpms
should work with a tar-ball of rear instead. Less convenient I think, but not
impossible.
We could also provide SVN/CVS to accomplish this.
What does fedora recommend?

In the rpmls output all directories have mode 755. I think Robert question was
to check if the /usr/share/rear directory was meant to be in read-only mode.
The short answer is yes. During a normal run (mkrescue/mkbackup workflow) rear
will not write nor modify anything under /usr/share/rear. We have /var/rear
which will be used to create the recovery information under.

Do not hesitate to ask if you need more clarification. We're happy to answer
and to comply as much as possible to fedora's rules.

best regards,
Gratien

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.