[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] Bumping version no. / build tag in banner
From: |
Felix |
Subject: |
Re: [Chicken-hackers] Bumping version no. / build tag in banner |
Date: |
Fri, 01 Jul 2011 08:22:24 +0200 (CEST) |
>> Is this necessary? library.c already has a dependency on version.scm.
>
> However, version.scm is currently included, not linked in. As I stated, if
> you include the version, build tag and branch in library.scm via an include
> (as now) you have to recompile it every time you bump any of them. That's
> quite slow. I don't like this delay and I assumed it would be a showstopper.
> With this change bumping a version is almost instant.
Why are you so concerned about build-times? Do you build chicken a lot?
>
>> The commit hash is only available when building from a git checkout.
>> Rebuilding everything from a tarball will have no way recover that
>> information.
>
> The git hash is irrelevant in a tarball, because it is built from a known
> tag, so I'm not sure why this matters. You can't get the current git branch
> from a tarball, either, but we still display it when available.
That's true.
>
> Anyway, this patch would not include the git hash stuff; it's mostly to fix
> the perpetually outdated build tags and branch tags when you are compiling
> from a git checkout. However, git hash is where I'm going with this in the
> end.
Could this be made smart enough to work even if the absence of ".git"?
cheers,
felix
- Re: [Chicken-hackers] Bumping version no. / build tag in banner,
Felix <=