"needle" name conflict
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp, debian
- Domain
- bioinformatics, cli
Research direction
No source files or tests are named. Start by locating the executable entry point and Debian packaging metadata, then review the Debian filename conflict described in the issue. Done requires an agreed replacement name that avoids the EMBOSS collision while preserving the program name expected by other packaging systems.
Written by the indexing model from the issue text.
Description
I put together a basic package of Needle for Debian and I discovered that there is another programs with the same name
/use/bin/needle is already provided by EMBOSS
https://packages.debian.org/bullseye/emboss a.k.a https://bio.tools/needle-ebi or https://bio.tools/needle
This causes a problem with Debian policy
Two different packages must not install programs with different functionality but with the same filenames. […] If this case happens, one of the programs must be renamed.
https://www.debian.org/doc/debian-policy/ch-files.html#binaries
And I would rather that the Debian package of Needle has the same program name as other packaging systems. Otherwise that causes problems for user's scripts and workflows..
Perhaps this Needle could be renamed? Sorry to ask it, but it would be best to not have the confusion.
- Dominant language
- C++
- Stars
- 16
- Forks
- 11
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seqan/needle
-
Needle 2.0.0 Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·