Menu

#24 Installation procedure/instructions are missing

open
nobody
None
5
2013-01-28
2012-01-28
Mikhail T.
No

As distributed the package lacks installation-instructions. Certainly, the library itself (in static and dynamic variant) should be installed, but what about the app-binaries? Are any of them considered "supported"? Also, what about the header files -- which are part of the API and which are "internal"?

The API-ones are expected to be supported in future releases... Please, consider adding proper install-targets to Makefiles or, at least, installation instructions in English to the documentation. Thank you!

Discussion

  • Mikhail T.

    Mikhail T. - 2012-01-29

    This is, how Debian are packaging udt-devel:
    http://packages.debian.org/wheezy/amd64/libudt-dev/filelist
    In other words, they install ALL header files, but don't compile ANY of the sample applications -- all of those are installed in source-code as examples.

    Is this the correct approach or should some of the header-files be unavailable from code, that's not part of UDT?

    Also, the apps seem to be useful on their own (and thus should be compiled and installed under bin/) -- is that correct, or are they meant as nothing but examples?

    I'm trying to create a FreeBSD port of UDT...

     
  • Yunhong Gu

    Yunhong Gu - 2012-01-29

    Only udt.h is required for application. All other headers are internal and no need to expose them in distribution.

    The programs in ./app directory are for testing purpose. I don't recommend to pack them in an installation package either.

     
  • Mikhail T.

    Mikhail T. - 2012-01-29

    Really? I thought, the utilities can be used out of the box -- and was going to install them as bin/udt-sendfile, bin/udt-recvfile, etc.

    Are they not usable out of the box like that? Shouldn't they be?

     

Log in to post a comment.