Skip to contentSkip to conversation

git tarballs gone?

DISCUSSION Gary Thomas 3 participants 7 messages Feb 10, 2011

lore
Share & tools
lore
#0 lore raw

I just noticed that with the new fetcher, git tarballs are no longer being created.
* Is this expected?
* Can it be [re]enabled? This is a great help to me so I can distribute pre-staged sources to my customers. Tarballs are much more convenient than .git repositories.

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 3 lines · Gary Thomas

I just noticed that with the new fetcher, git tarballs are no longer being created.
* Is this expected?

Not expected.

Quoted 4 lines

* Can it be [re]enabled? This is a great help to me so I can distribute pre-staged sources to my customers. Tarballs are much more convenient than .git repositories.

I will be looking into this shortly.

Sau!

Quoted 2 lines

Thanks

#2 lore raw
In reply to Gary Thomas
Quoted 6 lines · Gary Thomas

I just noticed that with the new fetcher, git tarballs are no longer being created.
* Is this expected?
* Can it be [re]enabled? This is a great help to me so I can distribute pre-staged sources to my customers. Tarballs are much more convenient than .git repositories.

Its expected, just set BB_GENERATE_MIRROR_TARBALLS = "1" in local.conf to generate them if you need them.

As standard the average user doesn't need/use/want them and the fetcher no longer needs them so we don't generate them by default any more.

Cheers,

Richard

#3 lore raw
Quoted 8 lines · Richard Purdie
Quoted 6 lines · Gary Thomas

I just noticed that with the new fetcher, git tarballs are no longer being created.
* Is this expected?
* Can it be [re]enabled? This is a great help to me so I can distribute pre-staged sources to my customers. Tarballs are much more convenient than .git repositories.

Quoted 5 lines

Its expected, just set BB_GENERATE_MIRROR_TARBALLS = "1" in local.conf to generate them if you need them.

As standard the average user doesn't need/use/want them and the fetcher no longer needs them so we don't generate them by default any more.

What would I need to do to get them generated? Here's what I tried (which did not work):

* I noticed that my build used git.pokylinux.org.matchbox-terminal, so

... set BB_GENERATE_MIRROR_TARBALLS in local.conf
% bitbake matchbox-terminal -c clean
% rm -f sstate-cache/*matchbox-terminal*
% bitbake matchbox-terminal

It seemed happy to use the stored GIT in downloads/git2/git.pokylinux.org.matchbox-terminal, but did not generate a tarball during the process.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#4 lore raw
Quoted 20 lines · Gary Thomas
Quoted 8 lines · Richard Purdie
Quoted 6 lines · Gary Thomas

I just noticed that with the new fetcher, git tarballs are no longer being created.
* Is this expected?
* Can it be [re]enabled? This is a great help to me so I can distribute pre-staged sources to my customers. Tarballs are much more convenient than .git repositories.

Quoted 5 lines

Its expected, just set BB_GENERATE_MIRROR_TARBALLS = "1" in local.conf to generate them if you need them.

As standard the average user doesn't need/use/want them and the fetcher no longer needs them so we don't generate them by default any more.

What would I need to do to get them generated? Here's what I tried (which did not work):

* I noticed that my build used git.pokylinux.org.matchbox-terminal, so

Quoted 7 lines

... set BB_GENERATE_MIRROR_TARBALLS in local.conf
% bitbake matchbox-terminal -c clean
% rm -f sstate-cache/*matchbox-terminal*
% bitbake matchbox-terminal

It seemed happy to use the stored GIT in downloads/git2/git.pokylinux.org.matchbox-terminal, but did not generate a tarball during the process.

That download directory already existed? It only updates the tarball if the repo changes:

os.chdir(ud.clonedir)
mirror_tarballs = data.getVar("BB_GENERATE_MIRROR_TARBALLS", d, True) if mirror_tarballs != "0" and ud.repochanged:
logger.info("Creating tarball of git repository") runfetchcmd("tar -czf %s %s" % (repofile, os.path.join(".") ),

(from git.py in the fetcher)

I guess we could make it do this if the destination file doesn't exist too, I'll add a patch to do that.

Cheers,

Richard

#5 lore raw
Quoted 13 lines · Richard Purdie
Quoted 2 lines · Gary Thomas

It seemed happy to use the stored GIT in downloads/git2/git.pokylinux.org.matchbox-terminal, but did not generate a tarball during the process.

That download directory already existed? It only updates the tarball if the repo changes:

os.chdir(ud.clonedir)
mirror_tarballs = data.getVar("BB_GENERATE_MIRROR_TARBALLS", d, True) if mirror_tarballs != "0" and ud.repochanged:
logger.info("Creating tarball of git repository") runfetchcmd("tar -czf %s %s" % (repofile, os.path.join(".") ),

Quoted 4 lines

(from git.py in the fetcher)

I guess we could make it do this if the destination file doesn't exist too, I'll add a patch to do that.

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=59a08262aba2d2b9b8b299a2818fb4cfe13b9909

It turned out to be a bit more ugly than I'd anticipated but a nice improvement.

Cheers,

Richard

#6 lore raw
Quoted 16 lines · Richard Purdie
Quoted 15 lines · Richard Purdie
Quoted 2 lines · Gary Thomas

It seemed happy to use the stored GIT in downloads/git2/git.pokylinux.org.matchbox-terminal, but did not generate a tarball during the process.

That download directory already existed? It only updates the tarball if the repo changes:

os.chdir(ud.clonedir)
mirror_tarballs = data.getVar("BB_GENERATE_MIRROR_TARBALLS", d, True) if mirror_tarballs != "0" and ud.repochanged:
logger.info("Creating tarball of git repository") runfetchcmd("tar -czf %s %s" % (repofile, os.path.join(".") ),

(from git.py in the fetcher)

Quoted 7 lines
Quoted 2 lines

I guess we could make it do this if the destination file doesn't exist too, I'll add a patch to do that.

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=59a08262aba2d2b9b8b299a2818fb4cfe13b9909

It turned out to be a bit more ugly than I'd anticipated but a nice improvement.

That did the trick; same experiment generated a tarball.

Thanks for the quick response!

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------