14 Feb
2012
14 Feb
'12
9:07 p.m.
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.
Thanks,
Francois
14 Feb
14 Feb
9:15 p.m.
New subject: [trinity-devel] Building tarballs from GIT
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.
Thanks,
Francois
Not publicly available at the moment, but you should get similar results
by tarring each TDE module separately and excluding the .git directory.
Tim
9:21 p.m.
New subject: [trinity-devel] Building tarballs from GIT
On Tue, 14 Feb 2012 22:07:16 +0100
François ANDRIOT <francois.andriot(a)free.fr> wrote:
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) ?
Thanks,
Francois
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
9:43 p.m.
New subject: [trinity-devel] Building tarballs from GIT
Le 14/02/2012 22:21, /dev/ammo42 a écrit :
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
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) ?
9:58 p.m.
New subject: [trinity-devel] Building tarballs from GIT
On Tue, 14 Feb 2012 22:43:29 +0100
Francois Andriot <francois.andriot(a)free.fr> wrote:
Le 14/02/2012 22:21, /dev/ammo42 a écrit :
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.
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) ? 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
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
15 Feb
15 Feb
5:59 a.m.
New subject: [trinity-devel] Building tarballs from GIT
Le 14/02/2012 22:58, /dev/ammo42 a écrit :
On Tue, 14 Feb 2012 22:43:29 +0100
Francois Andriot<francois.andriot(a)free.fr> wrote:
It does not work as expected either.
Francois
Le 14/02/2012 22:21, /dev/ammo42 a écrit :
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. 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) ?
6:55 a.m.
New subject: [trinity-devel] Building tarballs from GIT
Le 14/02/2012 22:58, /dev/ammo42 a écrit :
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
On Tue, 14 Feb 2012 22:43:29 +0100
Francois Andriot<francois.andriot(a)free.fr> wrote:
It does not work as expected either.
Francois Le 14/02/2012 22:21, /dev/ammo42 a écrit :
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. > 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. 
4:43 p.m.
New subject: [trinity-devel] Building tarballs from GIT
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.
--
David C. Rankin, J.D.,P.E.
9:46 p.m.
New subject: [trinity-devel] Building tarballs from GIT
On 02/14/2012 03:07 PM, François ANDRIOT wrote:
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.
Thanks,
Francois
NOT Official, but this script will get you started. Here is the help for it:
Usage: mkgittgz.sh path-to-tde [default ~/tde] dir-to-write-tgz [~/tdetgz] -w
[actually write!]
mkgittgz.sh will create tarballs from a local copy of the tde git repository
layout. The script requires the location of the local copy as the first argument
if the tde copy is not present in ~/tde and the directory to write tarballs to
[default ~/tdetgz]. The script will output all the tar commands as a test for
confirmation. Use the -w option as the third argument to actually create the files.
Filename format (examples):
tdepim-admin.tar.gz
tdepim-akregator.tar.gz
tdepim-certmanager.tar.gz
tdepim-cmake.tar.gz
NOTE: IT JUST OUTPUTS THE tar COMMANDS UNLESS YOU SUPPLY THE '-w' OPTION.
You can run it safely to confirm it will create the tarballs where and how you
want. Without the -w option you will get something similar to the following:
15:32 archangel:/dat_f/tde> sh ../david/scr/mkgittgz.sh /dat_f/tde
parent:
parent: applications
tar -C /dat_f/tde/main/applications -czf
/home/david/tdetgz/applications-abakus.tar.gz abakus
tar -C /dat_f/tde/main/applications -czf
/home/david/tdetgz/applications-adept.tar.gz adept
tar -C /dat_f/tde/main/applications -czf
/home/david/tdetgz/applications-amarok.tar.gz amarok
tar -C /dat_f/tde/main/applications -czf
/home/david/tdetgz/applications-basket.tar.gz basket
tar -C /dat_f/tde/main/applications -czf
/home/david/tdetgz/applications-bibletime.tar.gz bibletime
Hack it to suit your needs...
--
David C. Rankin, J.D.,P.E.
11:36 p.m.
New subject: [trinity-devel] Building tarballs from GIT
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
16 Feb
16 Feb
12:04 a.m.
New subject: [trinity-devel] Building tarballs from GIT
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 :)
--
David C. Rankin, J.D.,P.E.
12:06 a.m.
New subject: [trinity-devel] Building tarballs from GIT
On 15 February 2012 19:04, David C. Rankin
<drankinatty(a)suddenlinkmail.com> wrote:
On 02/15/2012 05:36 PM, Baho Utot wrote:
L0ner has them in the tde-packaging repository.
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/
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 :)
12:13 a.m.
New subject: [trinity-devel] Building tarballs from GIT
On 02/15/2012 06:06 PM, Calvin Morrison wrote:
L0ner has them in the tde-packaging repository.
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/
excellent! Also Pawels hal 0.5.14-8 fixed the boot hang. Never would have
clicked that the issue was a hardcoded directory for udev causing the issues.
--
David C. Rankin, J.D.,P.E.
6:17 p.m.
New subject: [trinity-devel] Building tarballs from GIT
On 02/15/2012 07:04 PM, David C. Rankin wrote:
On 02/15/2012 05:36 PM, Baho Utot wrote:
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
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 :)
4695
days inactive
4697
days old
13 comments
7 participants
participants (7)
-
/dev/ammo42 -
Baho Utot -
Calvin Morrison -
David C. Rankin -
Francois Andriot -
François ANDRIOT
-
Timothy Pearson