Message: previous - next
Month: July 2012

Re: [trinity-devel] What causes "checking for tde-config... not found" failures?

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 29 Jul 2012 16:29:03 -0500
On 07/28/2012 07:31 PM, Slávek Banko wrote:
> To build packages that yet not have v3.5.13-sru branch, should be taken from 
> their original v3.5.13, not the current git. You can use tag v3.5.13 for 
> checkout: git checkout v3.5.13


  How do I do the checkout?  I can see the tag in, but I can't check it out:

22:30 archangel:/dat_f/tde/tde/main/applications/kbookreader> git branch -l
* master
You have new mail in /var/mail/david
16:21 archangel:/dat_f/tde/tde/main/applications/kbookreader> git branch -r
  origin/HEAD -> origin/master
16:21 archangel:/dat_f/tde/tde/main/applications/kbookreader> git checkout v3.5.13
warning: unable to rmdir admin: Directory not empty
warning: unable to rmdir cmake: Directory not empty
Note: checking out 'v3.5.13'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 12476d8... Link most Trinity DSOs against the most common kdelibs
libraries to compensate for linking changes in modern distributions such as
Ubuntu Oneiric

  It looks like since it is a 'tag' and not a 'branch', git checkout won't work.
I've just downloaded the tarball and I'll try it that way. Let me know if you
have a better way, if not, I'll just go module by module and download the tarballs.

  Is there a link to a directory containing the tarballs somewhere? It would be
easier to just create a wget 'getfile' to download the modules that presently
have no v3.5.13-sru branch.

David C. Rankin, J.D.,P.E.