-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> On Thursday 06 November 2014 06.29:49 Michele Calgaro wrote:
>> Nightly builds are being rebuilt for RC1, but (...) I am writing from
>> such a
>> system, since I build all packages on my own
>>
>> :-) )
>>
>> Cheers
>>    Michele
>
> I'm not very experienced, but what is necessary to build packages? I
> assume
> one must get the source code, but what then? Is it possible with the tools
> provided by a standard distribution, what should I understand to manage
> such
> a task?

In general you want to do major development on a dedicated system (one
that you can wipe/reload if needed) due to the possibility of breaking
core components of TDE.  I'd recommend at least a dual-core machine with
several GB of RAM as well.

- From the software side, a standard Debian/Ubuntu install is a good base. 
You can install the base development packages with 'apt-get install
build-essential git', and install the build dependencies for a specific
package with 'apt-get build-dep <package name>'.

After a development system is set up, I like to hack on TDE packages with
the following method:
mkdir ~/TEMP
cd ~/TEMP
apt-get source <package name-trinity>
rm *
git clone https://<git username>@scm.trinitydesktop.org/scm/git/<package
name>
mv <package-name>/.git <package-name-revid-folder>
rm -rf package-name
cd <package-name-revid-folder>
dpkg-buildpackage -r fakeroot -b

That last command kicks off the build process; when done you get a series
of .debs in the folder above the source tree.  However, you don't have to
rerun that to build most changes you make to the source after the initial
build, usually you can just:

<edit sources>
cd obj-*
make install
<test>
<edit sources>
make install
<repeat>

Hope this helps some!

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlRhLJYACgkQLaxZSoRZrGFvZADcDwrxmX6LU0pb5iaaxXlkeaD9
12ohD1U9BLj9cADgweqQXRsieWjqjejtCj5ZWVC9zl8PJTOImfN/qg==
=nJot
-----END PGP SIGNATURE-----