Hi Alex Ameen,
Alex Ameen wrote:
This is a good question. I plan on making a new release this month.
When I first adopted the project I ambitiously thought I'd manage to create a
new release after about a month; but the truth is when I started doing a deep
dive into the internals
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
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
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
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,
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
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 confident
> this release will "do no harm". It was made for a
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 pass, there is high confidence of quality for the
systems it has been executed on.
On Sun, Feb 6, 2022 at 11:57 AM Daniel Herring wrote:
> I would personally recommend the "slow" process unless you are confident
> this release will "do no harm".
Hasn't it been slow enough already? Some say the project is finished.
rdie wrote:
On Sat, 2022-02-05 at 21:06 -0500, Mike Frysinger wrote:
On 05 Feb 2022 15:15, Alex Ameen wrote:
This is a good question. I plan on making a new release this month.
When I first adopted the project I ambitiously thought I'd manage to
create a new release after about a month; but the tru
On Sat, 2022-02-05 at 21:06 -0500, Mike Frysinger wrote:
> On 05 Feb 2022 15:15, Alex Ameen wrote:
> > This is a good question. I plan on making a new release this month.
> >
> > When I first adopted the project I ambitiously thought I'd manage to
> > create a new
On 05 Feb 2022 15:15, Alex Ameen wrote:
> This is a good question. I plan on making a new release this month.
>
> When I first adopted the project I ambitiously thought I'd manage to
> create a new release after about a month; but the truth is when I
> started do
This is a good question. I plan on making a new release this month.
When I first adopted the project I ambitiously thought I'd manage to
create a new release after about a month; but the truth is when I
started doing a deep dive into the internals there was a lot of history
and complexity
Alex,
can you estimate when you will be able to do a new release? Just to
tell people that the project is still alive :-)
Werner
On 2020-05-24 14:24:12 +0200, Marc Nieper-Wißkirchen wrote:
> Please excuse if this has been asked recently and I have missed it.
>
> I'd like to ask when or whether we can expect a new libtool release? Many
> improvements have happened since the last release. For example, many builds
> are
Please excuse if this has been asked recently and I have missed it.
I'd like to ask when or whether we can expect a new libtool release? Many
improvements have happened since the last release. For example, many builds
are plagued with the warning "ar: `u' modifier ignored since `D' is the
default
On Thu, 27 Sep 2018, Robert Boehne wrote:
I would be more than happy to cut a release, if only I could remember how.
I think the last version I released was 1.5.x - I'll look around but if
anyone on the list remembers where the instructions are - please help me
out ;)
I think that there are
On Thu, Sep 27, 2018 at 08:56:20AM -0700, Robert Boehne wrote:
> I would be more than happy to cut a release, if only I could remember how.
> I think the last version I released was 1.5.x - I'll look around but if
> anyone on the list remembers where the instructions are - please help me
> out ;)
I would be more than happy to cut a release, if only I could remember how.
I think the last version I released was 1.5.x - I'll look around but if
anyone on the list remembers where the instructions are - please help me
out ;)
Thanks,
Rob Boehne
On Fri, Sep 21, 2018 at 5:50 AM Samuel Tardieu
On Fri, 21 Sep 2018, Samuel Tardieu wrote:
Libtool is in need of additional volunteers to serve as maintainers to
help catch up on the backlog of patches/issues and prepare another
release.
My question was solely about tagging and cutting a new release from the
current state of the repository
tches/issues and prepare another
> release.
>
My question was solely about tagging and cutting a new release from the
current state of the repository so that patches contributed by volunteers
and accepted in the repository already get a more widespread distribution.
I understand how getting thro
On Fri, 21 Sep 2018, Samuel Tardieu wrote:
Would it be possible to cut a formal release?
Libtool is in need of additional volunteers to serve as maintainers to
help catch up on the backlog of patches/issues and prepare another
release.
Are you able to volunteer to be a libtool maintainer?
Hi.
Since libtool latest release 3 years ago, some important problems have
been patched. In particular, "-fuse-ld=…" is now propagated to the
driver when linking.
For example, it is not possible to build LLVM modules using libtool on
Ubuntu LTS using only released packages. "llvm-config
Is there any chance for cutting a new release with the OSX Yosemite
version parsing fix? This is going to affect a lot of users, and right
now there isn't even a released version of libtools to run reconfigure
with.
http://lists.gnu.org/archive/html/libtool-patches/2014-09/msg2.html
On 23 Oct 2014, at 15:06, Volker Braun vbraun.n...@gmail.com wrote:
Is there any chance for cutting a new release with the OSX Yosemite
version parsing fix? This is going to affect a lot of users, and right
now there isn't even a released version of libtools to run reconfigure
with.
http
25 matches
Mail list logo
