> Use menuselect's command line (--enable and --disable).
Great idea! How would you recommend generating the set of --enable and
--disable options that differ from the default from a build that was done?
--
_
-- Bandwidth and
On Fri, May 05, 2017 at 11:21:20AM -0400, Richard Kenner wrote:
> I'd like to be able to save the choices made in menuselect in a way
> that they can be tracked in a CM system and applied to a later release
> of Asterisk using an automated tool like Ansible. What's the best
> way to do that?
Use
On Friday 05 May 2017 at 16:52:39, Richard Kenner wrote:
> > Of course, you might run into problems if the later release introduces
> > new options (or deprecates old ones) which then aren't going to be in
> > your makeopts file
>
> That's my question: how do I reflect the changes that I made to
> Of course, you might run into problems if the later release introduces new
> options (or deprecates old ones) which then aren't going to be in your
> makeopts file
That's my question: how do I reflect the changes that I made to the
defaults in a way that's not dependent on the exact set of
On Friday 05 May 2017 at 16:21:20, Richard Kenner wrote:
> I'd like to be able to save the choices made in menuselect in a way
> that they can be tracked in a CM system and applied to a later release
> of Asterisk using an automated tool like Ansible. What's the best
> way to do that?
I'd like to be able to save the choices made in menuselect in a way
that they can be tracked in a CM system and applied to a later release
of Asterisk using an automated tool like Ansible. What's the best
way to do that?
--
_
