Hello,
thanks for your support! Indeed, after having worked the whole week-end on
it, I eventually come up with a few patches for the "autotoolisation" and
"header-burrying" feature (while of course remaining backward compatible),
and those patches can now be applied directly on the CVS trunk.
I have written a "patch applicator", which creates a temporary directory,
checks out SOCI's CVS trunk within it, downloads the patchs from
http://denisarnaud.fedorapeople.org/cvstrunk/ , and applies those patches to
the just-checked-out CVS code base. Then, "cvs diff" are created.
Way to proceed:
# Download the "patch applicator":
wget
http://denisarnaud.fedorapeople.org/cvstrunk/soci_apply_autotoolisation_patch.sh
# Give the execution right to the script
chmod 755
soci_apply_autotoolisation_patch.sh<http://denisarnaud.fedorapeople.org/cvstrunk/soci_apply_autotoolisation_patch.sh>
# Launch it: it creates a tmp directory
./soci_apply_autotoolisation_patch.sh<http://denisarnaud.fedorapeople.org/cvstrunk/soci_apply_autotoolisation_patch.sh>
I have still a small patch for the "Doxygenable" documentation, but it will
be for next time to automate it (if your are impatient, you can still see
here: https://opentrep.svn.sourceforge.net/svnroot/opentrep/trunk/soci/doc)!
In case, at some point, you agree to migrate to Subversion, I shall be able
to maintain SOCI from work, officially (I mean, I can devote time and energy
during my work on it), as a few important projects of my division now use it
[I made that decision :)], and I need to package properly those projects.
Moreover, in case you agree, I shall convert the tests so that they use
CPPUnit, so that we can monitor the quality with CruiseControl. We use that
stack, namely CPPUnit and CruiseControl, at work for several projects.
Hence, it should allow detecting regressions pretty fast.
As for the sustainability of the packaging for Fedora, I'm close to have
SOCI officially integrated into that distribution. And, as Fedora is kind of
the upstream version of RedHat, I shall strive to have SOCI officially
released for RedHat (from version 5). The packagers have to commit to
maintain such packages for... seven years (the duration of the support for
RedHat)! So, I guess it should be enough!
However, in case you agree to integrate those few changes, it will greatly
simplify my work of packager after that. Until then, I must spend a lot of
time and energy to keep both versions (CVS and SVN) synchronised...
Thanks again for your great job (in having developed SOCI)!
Best Regards
Denis
PS: I'm more a developer than a packager (so, I can of course contribute to
the C++ code as well)
2009/4/20 Denis Arnaud <[email protected]>
>
> De: Maciej Sobczak <[email protected]>
> Objet: Re: [SOCI-users] RPM packaging for Fedora (and other RPM-based
> distributions)
> À: "General-purpose list for SOCI users." <
> [email protected]>
> Date: Dimanche 19 Avril 2009, 22h08
>
> Hello,
>
> Mateusz Loskot wrote:
>
> > Over this weekend, I will take a look at them and try to incorporate.
> >
> > Maciek, do you agree?
>
> Yes.
> There is just one thing that we need to figure out before that, though.
>
> I was always under the impression that the ready to use packages are
> most effectively prepared by people who are associated with a particular
> package system or a particular Linux distribution and not necessarily by
> the original projects. The point is that there are many packaging
> systems and it requires lots of dedication to keep the packages well
> maintained.
> The approach where the development team focuses on the code and where
> the maintainers associated with particular distro take care of the
> packaging seems to be effective in the sense that it better reflects the
> competencies of those who do the work.
> The above approach is not universal, however, and there are projects
> that take care of packaging as well. Should we do the same?
>
> We are in a good situation now that Denis simply contributes his work -
> thank you Denis for this! Without this it would be pretty clear that we
> should not get involved in package preparation.
> I think that the best what we can do is to integrate this contribution
> in the CVS tree and provide RPM packages on our download page, together
> with the "raw" tar.gz/zip packages. Thanks to this, people will be able
> to choose the package that is most appropriate for them.
>
> It should be still clear that this work, similarly to autotools, relies
> on the availability of the maintainer to keep things going in the future
> - without this we will be force to drop that part in next releases, very
> likely leading again to the (unnecessary) grief among those who are used
> to it. The whole project is of course based on voluntary effort, but
> please remember also that adding something to the project means taking
> responsibility for it tomorrow.
>
> Mateusz, as our "package and build manager" ;-), please try to work
> together with Denis to get this going. If you manage to get the
> autotools working again, feel free to resurrect them as well.
>
> Interesting - is there a possibility to make SOCI an official package in
> any of the Linux distributions? Do you consider it to be good, instead
> of or in addition to providing independent releases from SourceForge?
>
> Again, thank you very much Denis for this contribution.
>
> Regards,
>
> --
> Maciej Sobczak * www.msobczak.com * www.inspirel.com
>
>
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
