10 Sep
2010
10 Sep
'10
4:51 p.m.
I want to test my build scripts against source
tarballs. How do you plan
to provide source tarballs when 3.5.12 goes official?
Most likely in two forms; one tarball for each module and application, and
also one large tarball containing all modules and applications, with the
individual tarballs contained therein. Each individual tarball will
contain the application and a copy of the shared admin directory required
to build it.
To test here, I presume I need to strip the svn
directory of the svn files
and directories. Yet how are you planning to provide the make and
configure files in tarballs?
Are you going to provide static snapshots of the make and configure files,
as was the practice back in the original KDE tarball days, or are you
going to expect end-users to build those files like we do now with svn?
With the variety of platforms Trinity targets, I am concerned that
providing static configure and make files will be more trouble than it is
worth. You can get very strange errors if the automake files on the
system are even a slightly different version than those that generated the
static files (trust me, been there done that!). Now consider that Trinity
officially supports Debian Lenny through Ubuntu Maverick (at this point)
and I think you have a recipe for disaster.
I'll probably copy the instructions off the Wiki and place them in a text
file called BUILDING or similar.
Thoughts? Comments?
Tim