Debian - netcat build deps #2195
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
[Steffen Möller]
Apparently the former netcat package was renamed to netcat-traditional
(https://tracker.debian.org/pkg/netcat).
The 'netcat' name is a virtual package provided by several:
% apt-cache search --names-only netcat
netcat - TCP/IP swiss army knife -- transitional package
netcat-traditional - TCP/IP swiss army knife
netcat-openbsd - TCP/IP swiss army knife
netcat-traditional-dbgsym - debug symbols for netcat-traditional
netcat-openbsd-dbgsym - debug symbols for netcat-openbsd
%
If we want to pick one of them as the preferred one, I suspect we should
put the wanted one first and the virtual name after this, ie
netcat-traditional | netcat
…--
Happy hacking
Petter Reinholdtsen
|
Collaborator
|
@smoe When do you plan to complete this draft patch? |
smoe
force-pushed
the
netcat_build_deps
branch
from
3bb62be to
034dafe
Compare
Collaborator
Author
|
Done. Thanks for pushing me to push. On a sidenote - did you find where netcat is used during the build process? |
Collaborator
|
[Steffen Möller]
Done. Thanks for pushing me to push. On a sidenote - did you find
where netcat is used during the build process?
No, did not investigate. Assumed you had and that it is used. Did you
not find it?
…--
Happy hacking
Petter Reinholdtsen
|
Collaborator
|
I tested build without netcat, only to discover nc is used by several tests, for example tests/linuxcncrsh-tcp/. |
Collaborator
Author
|
Are we respecting the DEB_BUILD_OPTIONS=nocheck to warrant the <!nocheck> for clarity? https://wiki.debian.org/BuildProfileSpec |
Collaborator
Author
|
What came to mind was that we could have an RTAI build profile and use that to substitute what debian/configure is addressing today. |
Collaborator
|
[Steffen Möller]
Are we respecting the DEB_BUILD_OPTIONS=nocheck to warrant the
<!nocheck> for clarity? https://wiki.debian.org/BuildProfileSpec
No one implemented this, as far as I know.
What came to mind was that we could have an RTAI build profile and use
that to substitute what debian/configure is addressing today.
See <URL: #1835 >.
…--
Happy hacking
Petter Reinholdtsen
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apparently the former netcat package was renamed to netcat-traditional (https://tracker.debian.org/pkg/netcat).