Bugzilla Bug 82447

Hi,

Box Backup is an open source, completely automatic on-line backup system for UNIX. See also http://www.fluffy.co.uk/boxbackup/. The attached .tar.gz file contains an ebuild, init scripts and configuration files.

Mark

Created an attachment (id=51508) [details]
boxbackup-0.09.ebuild (new package)

*** Bug 71995 has been marked as a duplicate of this bug. ***

does anyone from app-backup herd object if I take this ebuild?

Mark, thanks for the ebuild.
- Is there a reason why you force -j1 for make?
- For calling configure, there is a handly "econf" thing, like "emake", did you
decide not to use it deliberately?
- It's quite unconventional to install files yourself in src_install(), why
don't you use "make DESTDIR=${D} install"?
- for adding and removing users/groups there are tools "enewuser" and "enewgroup"

Could you try to elaborate on/implement the points mentioned above in a new
ebuild, preferably via a patch with the current one?

grobian: no problems with you coming on to help us in app-backup.

I'm waiting for any response from recruiters to get app-backup up to speed (got
2 people waiting), so please add yourself to the herd and the mailing alias (I'd
like to keep the assigned group in bugzilla as app-backup, for tracking reasons).

in response to comment #3:

ok, I had not realised that there still exist people that think it's better to
create your own configure script in Perl, as well as don't care about (g)make
and go for bsdmake if necessary and do the install phase via a few scripts.

(horror)

However, I managed to get this thing compiling on x86 and ppc-macos using GCC4.
 I think it also compiles on solaris, as I applied a solaris patch that's on the
boxbackup website.  Altogether some patchwork and unavoidable sed replacements
to get the code somehow GCC4 proof.

Mark, thanks for figuring out most of the job of manually installing the files.
 How much you think it is required to generate the config file whenever your
conf.d file changes?  Since the conf.d does not seem to hold actual settings
that influence how the daemon is started, I'd prefer just to have the config
file in /etc and not be auto-generated upon change of the conf.d file...

Created an attachment (id=67138) [details]
Ebuild boxbackup client part

Created an attachment (id=67139) [details]
Ebuid boxbackup clent part with conf & init files

Created an attachment (id=67140) [details]
Ebuild boxbackup server part

Created an attachment (id=67141) [details]
Ebuid boxbackup server part with conf & init files

Created an attachment (id=67145) [details]
Ebuild with fix

Created an attachment (id=67146) [details]
Ebuid boxbackup clent part with conf & init files. Fix

Created an attachment (id=67147) [details]
Ebuild with fix

Anatoly, what versions does your ebuilds deal with?

I'll look at them in more detail later, thanks sofar.

Created an attachment (id=67148) [details]
Ebuid boxbackup server part with conf & init files. Fix

(In reply to comment #13)
> Anatoly, what versions does your ebuilds deal with?
It's my variant ebuild's for boxbackup. Obsolete ebuid contains "econf" but
configure in package not compatibility with this, i'm rollback to old version.
With ./configure.

> I'll look at them in more detail later, thanks sofar.
10x. 

PS Boxbackup very usefull backup software ;)

Created an attachment (id=67150) [details]
files/boxbackup-0.09-solaris.patch -- a modified version of the solaris patch
on the boxbackup website

I have worked on this ebuild myself in the past.  I will submit my files that I
modified/created that represent my efforts to get boxbackup working on
ppc-macos too.

Created an attachment (id=67151) [details]
files/boxbackup-0.09-darwin.patch -- a patch for darwin systems

this patch allows compilation of boxbackup 0.09 on OSX 10.4

Created an attachment (id=67152) [details]
boxbackup-0.09.ebuild -- a modified version of the original ebuild supplied by
Mark Spanbroek

I made an attempt to generalise the ebuild supplied by Mark Spanbroek, comment
it a bit on why things are not done the standard ways.

This ebuild uses one source file for both client and server.  Anatoly, it
looked in your ebuilds as if there are two source files, one for client and the
other for server, but I can't find them on sourceforge.  Do you have access to
development sources of boxbackup?

Created an attachment (id=68657) [details]
boxbackup-0.09.ebuild v0.2

I made some improvements on compilation area, and included the patch made by
Alexandrai to the sources to set the paths right.  We can now do without sed
crap to compile on GCC4

Created an attachment (id=68658) [details]
boxbackup-0.09-gentoo.patch

patch extracted from Anatoly's files (sorry, got your name wrong in previous
post)

it makes no sense to spam the ppc-macos guys at this moment

Created an attachment (id=68661) [details]
files/bbackupd.rc  -- init script for bbackupd

This is a modified version of the init script from the first attachment (the
tar.gz). I removed the automatic (re)generation of config files from the init
script, because that really isn't the place to do it.

Created an attachment (id=68663) [details]
files/bbackupd.rc  -- init script for bbstored

Same change for the bbstored init script.

Ok, I checked in a boxbackup ebuild largerly based on the work of Mark
Spanbroek, including the gentoo patches by Anatoly Shipitsin.  It compiles and
runs on ~x86.

Please open a new bug if problems appear.