Hi Everyone,
As discussed before on this list, and after the recent name change,
extracting a versionned ("upstream official")
tarball from the git repositories for targetcli, configshell and
rtslib is now a lot easier.
The top-level Makefiles of the git repositories now have a 'release'
target. This generates a tarball in dist/ to be
used as official upstream archive for distributions and end-users.
That tarball also contains a debian/ tree and
an rpm specfile at its root, allowing end-users to easily generate rpm
and debian packages the usual way
(dpkg-builpackage / rpmbuild). Other than that, the tarball is clean
and does not have some of the extra
files relevant only to the git tree. Of course, the code in the
tarball contains all versionning information.
FYI, the rpm specfiles and debian changelogs found in the release
tarballs contain the whole git version
history.
There are also two helper targets in the git tree Makefile allowing
one to directly generate rpm and debian
packages ('make rpm' and 'make deb'). Those targets are using the
exact same tarball generated by
'make release'.
Also, the documentation build process for configshell and rtslib has
been moved to the packaging scripts,
so that individual maintainers can alter the process if needed. A
side-effect is that the documentation build
process now benefits from the packaging build dependencies system. As
for targetcli, the doc package has
been simply removed, as it was just a stub containing empty pdf and
html files. The shell is self-documented,
so the lack of external documentation should not be a problem.
The current version/tags, after the release tarball addition and some
minor changes currently are:
- rtslib version 2.1
- configshell version 1.1
- targetcli version 2.0rc1
I'll wait for some user feedback before tagging 2.0, please test the
rc1 and let me know how it goes.
Best Regards,
--
Jérôme Martin
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
