On 2022-02-06 19:49:36 -0500, Mike Frysinger wrote:
> the repository is pinned to a specific commit as you can see online:
> https://git.savannah.gnu.org/cgit/libtool.git/log/gnulib
>
> so the normal git clone + submodule sync requires a sha1 collision.
>
> if someone were to manually update the
On 07 Feb 2022 09:32, Vincent Lefevre wrote:
> what is done on Debian (where the libtool uses the version from the
> gnulib package, so that it is interesting to know the behavior with
> the current gnulib).
eh ? packages that leverage gnulib don't get libtool from gnulib. they
get it from libto
On Sun, Feb 6, 2022 at 8:02 PM Mike Frysinger wrote:
>
> On 06 Feb 2022 11:56, Daniel Herring wrote:
> > FWIW, libtool is a particularly difficult code base to release. Long
> > history, many users, multi-platform, ...
> >
> > I would personally recommend the "slow" process unless you are confide
On 2022-02-07 05:43:11 -0500, Mike Frysinger wrote:
> On 07 Feb 2022 09:32, Vincent Lefevre wrote:
> > what is done on Debian (where the libtool uses the version from the
> > gnulib package, so that it is interesting to know the behavior with
> > the current gnulib).
>
> eh ? packages that levera
Thanks for all of the advice y'all.
I'm going to get this release together as soon as possible and resolve
issues from there.
I agree that paralysis set in a bit as a result of me trying to test a bit
overboard on my own ( lots of VMs ). I appreciate the reality check :)
On Mon, Feb 7, 2022, 4:5
No worries. Glad someone is carrying the project forward.
Next time, consider using the "slow process" as "outsourced QA testing".
It might be easier and faster. :)
-- Daniel
On Mon, 7 Feb 2022, Alex Ameen wrote:
Thanks for all of the advice y'all.
I'm going to get this release together
Hi Alex,
Feel free to reach out if you have pending patches/issues you want to
"bump", ideas for improvements, general advice for a new GNU maintainer
- and above all if you'd like to lend a hand toward getting `libtool' up
and running again.
Many thanks for your work on Libtool!
I believe
On 2/8/22, Julien ÉLIE wrote:
> Hi Alex,
>
>> Feel free to reach out if you have pending patches/issues you want to
>> "bump", ideas for improvements, general advice for a new GNU maintainer
>> - and above all if you'd like to lend a hand toward getting `libtool' up
>> and running again.
>
> Many
On Mon, 7 Feb 2022 12:14:29 -0600
Alex Ameen wrote:
> Thanks for all of the advice y'all.
>
> I'm going to get this release together as soon as possible and resolve
> issues from there.
>
> I agree that paralysis set in a bit as a result of me trying to test
> a bit overboard on my own ( lots o
On Sun, 6 Feb 2022 12:21:34 -0600 (CST)
Bob Friesenhahn wrote:
> On Sun, 6 Feb 2022, Daniel Herring wrote:
> >
> > In my opinion, frequent slow releases are way better than rare fast
> > releases.
>
> That may be true for some software, but libtool has a really good
> test suite so if tests pa
10 matches
Mail list logo
