Le 14/02/2012 22:21, /dev/ammo42 a écrit :

...

Hello, I'd like to know if there is an existing script or method to build "official" source tarballs from git. I need to get tarballs that "look like" the ones that are delivered for official releases, e.g. that I can build exactly in the same way that I build official releases tarballs.

git-archive(1) ?

Hello, of course I've found that I can simply tar the existing Git directory structure. But the resulting archive does not contain some required folders (like "admin" or "cmake"), which are in fact located elsewhere in the Git repo. So my question was more precisely: is there a script that "intelligently" builds the final TDE tarballs, converting those links to actual content, and any other trick that I'm not aware of ?

Thanks Francois

Le 14/02/2012 22:58, /dev/ammo42 a écrit :

On Tue, 14 Feb 2012 22:43:29 +0100 Francois Andriotfrancois.andriot@free.fr wrote:

...

Le 14/02/2012 22:21, /dev/ammo42 a écrit :

...

...

Hello, I'd like to know if there is an existing script or method to build "official" source tarballs from git. I need to get tarballs that "look like" the ones that are delivered for official releases, e.g. that I can build exactly in the same way that I build official releases tarballs.

git-archive(1) ?

Hello, of course I've found that I can simply tar the existing Git directory structure.

I was not talking about using tar directly but the "git archive" command, which according to the manpages seems to do what you want. But since I didn't actually try it I don't know if it behaves well with admin and cmake folders.

It does not work as expected either.

Francois

On 02/15/2012 12:55 AM, Timothy Pearson wrote:

Right, I wouldn't expect it to, as the GIT submodule feature is one of the weakest points of GIT. When I generate the release tarballs I do so from a full copy of the entire GIT tree, submodules and all, and walk the tree down to each module (e.g. tdelibs, tdenetwork, amarok, etc.) to generate a tarball of each module.

Tim

Francois, all,

I have one for the old svn tree that I could tweak for git. Basically you just read the dir structure into an array or dump it to a file by changing into the tde dir and issuing:

find main/ -maxdepth 2 -type d

That will give you a dir list that you can use to walk the tree and create tarballs of the modules you want. You just need to exclude the directories that you don't want zip.

Then just loop though the list and create tarballs. See 'tar --help' and look at the '-C, --directory=DIR' option to limit the directory information you want in your tarballs.

On 02/15/2012 04:46 PM, David C. Rankin wrote:

Hack it to suit your needs... for f in ${_pkg[@]}; do

Hack in progress ;)

This might be better for the section

# create your tarballs --->

for d in ${tdedirs[@]}; do

instead of

for((i=0;i<${#tdedirs[@]};i++)); do

<---

The you can use ${d} instead of

# set current directory current="${tdedirs[$i]}"

for example

dirs=( $(find . -maxdepth 2 -type d | sort) ) for d in ${tdedirs[@]}; do echo ${d} done

or you can reduce it to just

for d in $(find . -maxdepth 2 -type d | sort); do echo "We be looking into ---> ${d}" echo "Do stuff here like taring the directory" done

On 15 February 2012 19:04, David C. Rankin drankinatty@suddenlinkmail.com wrote:

On 02/15/2012 05:36 PM, Baho Utot wrote:

...

Hack in progress ;)

This might be better for the section

# create your tarballs  --->

for d in ${tdedirs[@]}; do

instead of

for((i=0;i<${#tdedirs[@]};i++)); do

<---

The you can use ${d} instead of

# set current directory   current="${tdedirs[$i]}"

Yep, you are correct!  But, I originally was using a double loop (for i in ... for j in ...) to parse each module (tdepim, etc..) and then I would manipulate the i loop index at the end of the j loop ((i+=j)) to jump to the next module :)

It just depends :)

I'll keep my latest in:

http://www.3111skyline.com/dl/dt/trinity/scr/mkgittgz.sh

currently just clean up typos in comments and the echo to output:

Entering Module: ${parent}

instead of

parent: ${parent}

Also, do you have PKGBUILDs for the current 3.5.13? All mine a ~1 year old now and it would be awesome if I could avoid rebuilding the wheel :)

L0ner has them in the tde-packaging repository.

http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/

On 02/15/2012 07:04 PM, David C. Rankin wrote:

On 02/15/2012 05:36 PM, Baho Utot wrote:

...

Hack in progress ;)

This might be better for the section

# create your tarballs --->

for d in ${tdedirs[@]}; do

instead of

for((i=0;i<${#tdedirs[@]};i++)); do

<---

The you can use ${d} instead of

# set current directory current="${tdedirs[$i]}"

Yep, you are correct! But, I originally was using a double loop (for i in ... for j in ...) to parse each module (tdepim, etc..) and then I would manipulate the i loop index at the end of the j loop ((i+=j)) to jump to the next module :)

It just depends :)

I'll keep my latest in:

http://www.3111skyline.com/dl/dt/trinity/scr/mkgittgz.sh

currently just clean up typos in comments and the echo to output:

Entering Module: ${parent}

instead of

parent: ${parent}

Also, do you have PKGBUILDs for the current 3.5.13? All mine a ~1 year old now and it would be awesome if I could avoid rebuilding the wheel :)

Yes, these build from the 3.5.13 tarballs and not git.

https://github.com/baho-utot/trinity

git clone github.com:baho-utot/trinity.git