Recent

Author Topic: Unit contribution to fpc, where to put non-package package dependencies?  (Read 885 times)

Leledumbo

  • Hero Member
  • *****
  • Posts: 8836
  • Programming + Glam Metal + Tae Kwon Do = Me
I want to contribute a FPC friendly licensed Redis interface unit, which will be the base for the upcoming redis backed websession implementation.

I use lNet as the networking library, but it's not a FPC package yet. I know fppkg makes use of it by including its source in the fppkg source directory, and certainly reusing that is an option. But is it allowed from FPC packaging POV? Or is there any more recommended way?

Attached is the current state of the package, which practically can send any commands but can only parse (bulk) string response as of now, with an example.

 

TinyPortal © 2005-2018