On 2019-04-01 I wrote:
> Here's the proposed gitsub.sh script (to be shared through gnulib,
> outside of any module, like 'bootstrap'):
> == gitsub.sh
> ==
After I made a couple of corrections to this script on 2019-04-02, I am
using
Hello Daiki,
> I wanted to express my motivation
> behind the switch to using "git submodule" in gettext. That was not for
> making upgrades easier, but for making change tracking easier.
> ... That was making "git bisect" hard.
I'm not turning off git submodules in gettext. I'm also not suggest
Hello Bruno,
Bruno Haible writes:
> On 2019-03-03 I listed the problems that I have with the existing practices
> of using gnulib as a submodule.
>
> Here's my attempt to fix this for the packages I maintain (gettext,
> libunistring, etc.). It's a new script 'gitsub.sh'.
I should have commented
Bernhard Voelker wrote:
> Additionally to updating gnulib, often some projects need to sync additional
> files from the freshly updated gnulib subdirectory, like e.g. bootstrap or
> COPYING.
> ...
> WDYT?
Copying files is one thing; that can be done wherever in your build system
(autogen.sh, boot
Hi,
On 2019-03-03 I listed the problems that I have with the existing practices
of using gnulib as a submodule.
Here's my attempt to fix this for the packages I maintain (gettext,
libunistring, etc.). It's a new script 'gitsub.sh'.
The main point is a clear separation between git / version contr
On 3/3/19 7:03 PM, Bruno Haible wrote:
> 2) A submodule has to be upgraded occasionally. bootstrap/autogen.sh does
> not help doing this. I have to keep a command in a cheat-sheet:
>$ (cd gnulib && git fetch && git merge origin/master); git add gnulib
Additionally to updating gnulib
Hi Gary,
> ... entirely sufficient for:
>
> 1. running on a freshly cloned working copy to set everything up ready for
> ./configure && make
>
> 2. rebootstrapping after updating submodules
Yes, it is sufficient for the "simple" cases.
What the current bootstrap is not good at:
* Keeping t
On 03.03.19 19:03, Bruno Haible wrote:
> Hi,
>
> When gnulib is used in a package, often the maintainers of that package
> use it via a git submodule, because that enables them to upgrade to newer
> versions of gnulib when they want to (and have a failsafe build between
> these upgrades), rather t
> On Mar 3, 2019, at 10:03 AM, Bruno Haible wrote:
>
> Hi,
>
> When gnulib is used in a package, often the maintainers of that package
> use it via a git submodule, because that enables them to upgrade to newer
> versions of gnulib when they want to (and have a failsafe build between
> these u
Hi,
When gnulib is used in a package, often the maintainers of that package
use it via a git submodule, because that enables them to upgrade to newer
versions of gnulib when they want to (and have a failsafe build between
these upgrades), rather than having to adapt to gnulib changes at any moment
10 matches
Mail list logo
