On 7/4/2022 3:52 am, Joel Sherrill wrote: > On Wed, Apr 6, 2022 at 12:27 PM Gedare Bloom <ged...@rtems.org> wrote: > >> On Wed, Apr 6, 2022 at 9:23 AM Sebastian Huber >> <sebastian.hu...@embedded-brains.de> wrote: >>> >>> On 06/04/2022 17:09, Joel Sherrill wrote: >>>> On Wed, Apr 6, 2022 at 10:03 AM Sebastian Huber >>>> <sebastian.hu...@embedded-brains.de >>>> <mailto:sebastian.hu...@embedded-brains.de>> wrote: >>>> >>>> On 06/04/2022 17:01, Joel Sherrill wrote: >>>> > This needs a ticket and a target of 7. >>>> >>>> A ticket, yes, but do you really want to ship a completely >> outdated web >>>> server with RTEMS 6? >>>> >>>> >>>> We have no replacement. I added a ticket to get CivitWeb ported. That >> would >>>> be the better solution -- replacement. Not dropping functionality. >>> >>> Both civitweb (for example v1.15) and mongoose work with RTEMS. >>> >> >> We need to be more aggressive about dropping network services that are >> unmaintained. If someone really ants it, they can revive it and take >> on the debt themselves. I think it would be good to have documentation >> how to use Civetweb. >> > > I'd be thrilled to see some documentation on Civitweb as a trade for > removing this before 6.
I would like to see how we resolve this. There is no dependency in the code so it can be removed and I think it is a good thing to to however we need a way for users to use the code and/or migrate. > It still needs a ticket though. Yeap. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
