Menu

#491 mhparam change in nmh 1.7

Unassigned
closed-fixed
None
5
2023-01-21
2018-01-12
Mike Kupfer
No

From the nmh-1.7-RC3 NEWS:

  • With the move of support binaries from ${libdir} to
    ${libexecdir}/nmh, the mostly undocumented 'libdir' mhparam(1)
    component has been replaced by a new 'libexecdir' component.
    'libdir' will be removed in a future release.

We'll need to track this change in MH-E.

Related

Tickets: #491

Discussion

  • Mike Kupfer

    Mike Kupfer - 2018-01-12
    • status: unread --> open
     
  • Darel

    Darel - 2018-01-12

    Will making any changes to MH-E because of the external nmh programs ( mhparam, etc.) cause any problems with gnu-mh (mailutils) libraries usage to those of use who use it?

    darel

    Mike Kupfer via mh-e-devel mh-e-devel@lists.sourceforge.net wrote:

    • status: unread --> open

    [bugs:#491] mhparam change in nmh 1.7

    Status: open
    Milestone: Unassigned
    Created: Fri Jan 12, 2018 02:20 AM UTC by Mike Kupfer
    Last Updated: Fri Jan 12, 2018 02:20 AM UTC
    Owner: nobody

    From the nmh-1.7-RC3 NEWS:

    * With the move of support binaries from ${libdir} to
      ${libexecdir}/nmh, the mostly undocumented 'libdir' mhparam(1)
      component has been replaced by a new 'libexecdir' component.
      'libdir' will be removed in a future release.
    

    We'll need to track this change in MH-E.


    Sent from sourceforge.net because mh-e-devel@lists.sourceforge.net is
    subscribed to https://sourceforge.net/p/mh-e/bugs/

    To unsubscribe from further messages, a project admin can change
    settings at https://sourceforge.net/p/mh-e/admin/bugs/options. Or, if
    this is a mailing list, you can unsubscribe from the mailing list.


    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot


    mh-e-devel mailing list
    mh-e-devel@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/mh-e-devel

     

    Related

    Tickets: #491

    • Bill Wohler

      Bill Wohler - 2018-01-12

      Hi Darel,

      I don't think so.

      The function mh-variant-gnu-mh-info has its own copy of the libdir
      component. We'd have to update the mh-variant-nmh-info component,
      probably by allowing both for backwards compatibility.

      We'd also have to look for both in mh-variant-mh-info which starts the
      process.

      Darel via mh-e-devel mh-e-devel@lists.sourceforge.net wrote:

      Will making any changes to MH-E because of the external nmh programs ( mhparam,
      etc.) cause any problems with gnu-mh (mailutils) libraries usage to those of use who
      use it?

      darel

      Mike Kupfer via mh-e-devel mh-e-devel@lists.sourceforge.net wrote:

        + status: unread --> open
      --------------------------------------------------------------------------------
      
      [bugs:#491] mhparam change in nmh 1.7
      
      Status: open
      Milestone: Unassigned
      Created: Fri Jan 12, 2018 02:20 AM UTC by Mike Kupfer
      Last Updated: Fri Jan 12, 2018 02:20 AM UTC
      Owner: nobody
      
      From the nmh-1.7-RC3 NEWS:
      
      * With the move of support binaries from ${libdir} to
        ${libexecdir}/nmh, the mostly undocumented 'libdir' mhparam(1)
        component has been replaced by a new 'libexecdir' component.
        'libdir' will be removed in a future release.
      
      We'll need to track this change in MH-E.
      
      --------------------------------------------------------------------------------
      
      Sent from sourceforge.net because mh-e-devel@lists.sourceforge.net is
      subscribed to https://sourceforge.net/p/mh-e/bugs/
      
      To unsubscribe from further messages, a project admin can change
      settings at https://sourceforge.net/p/mh-e/admin/bugs/options. Or, if
      this is a mailing list, you can unsubscribe from the mailing list.
      
      --------------------------------------------------------------------------------
      
      Check out the vibrant tech community on one of the world's most
      engaging tech sites, Slashdot.org! http://sdm.link/slashdot
      
      --------------------------------------------------------------------------------
      
      mh-e-devel mailing list
      mh-e-devel@lists.sourceforge.net
      https://lists.sourceforge.net/lists/listinfo/mh-e-devel
      

      [bugs:#491] mhparam change in nmh 1.7

      Status: open
      Milestone: Unassigned
      Created: Fri Jan 12, 2018 02:20 AM UTC by Mike Kupfer
      Last Updated: Fri Jan 12, 2018 02:20 AM UTC
      Owner: nobody

      From the nmh-1.7-RC3 NEWS:

        + With the move of support binaries from ${libdir} to
          ${libexecdir}/nmh, the mostly undocumented 'libdir' mhparam(1)
          component has been replaced by a new 'libexecdir' component.
          'libdir' will be removed in a future release.
      

      We'll need to track this change in MH-E.


      Sent from sourceforge.net because mh-e-devel@lists.sourceforge.net is subscribed to
      https://sourceforge.net/p/mh-e/bugs/

      To unsubscribe from further messages, a project admin can change settings at
      https://sourceforge.net/p/mh-e/admin/bugs/options. Or, if this is a mailing list,
      you can unsubscribe from the mailing list.


      Alternatives:

      ----------------------------------------------------

      Check out the vibrant tech community on one of the world's most
      engaging tech sites, Slashdot.org! http://sdm.link/slashdot


      mh-e-devel mailing list
      mh-e-devel@lists.sourceforge.net
      https://lists.sourceforge.net/lists/listinfo/mh-e-devel

      --
      Bill Wohler wohler@newt.com aka Bill.Wohler@nasa.gov
      http://www.newt.com/wohler/
      GnuPG ID:610BD9AD

       

      Related

      Tickets: #491

  • Bill Wohler

    Bill Wohler - 2018-09-25

    Test comment, please ignore.

     
  • Mike Kupfer

    Mike Kupfer - 2023-01-21
    • status: open --> closed-fixed
    • assigned_to: Mike Kupfer
     
  • Mike Kupfer

    Mike Kupfer - 2023-01-21

    The fix for this will be in Emacs 29.1 (commit b3de81a6ee3).

     

Log in to post a comment.