Display MoreWhy?! It doesn't make sense!
Each imo has its own files to read...
Also, there are some features in ncam that aren't in oscam, so ncam needs its own files to read them, not oscam
If you want to unify the files, do it manually... delete the ncam file and create a symlink ... for example, the ncam.conf and oscam.conf files with this command.
However, in this case, there will be no support if your ncam doesn't work or doesn't open encrypted channels... you must troubleshoot the errors yourself.
Actually I was thinking about this suggestion before, why have separate files contain almost same data.....
So I asked about the benefits of it, I don't want to push in spacific direction but it just idea to discuss
**Proposal for File Unification Between OSCam and NCam**
After examining both codebases, it appears there's significant redundancy in many core files (readers, servers, etc.) that could benefit from unification. Key observations:
1. **Code Duplication**: Approximately 70-80% of reader/server implementation files contain identical or nearly identical code between projects
2. **Maintenance Burden**: Currently, bug fixes/enhancements often need to be manually ported between projects
3. **Divergence Points**: Where NCam requires unique functionality (e.g., specific protocol support), these could remain as separate extensions
**Suggested Approach**:
- Create a shared core module for common components (readers, servers, etc.)
- Maintain project-specific extensions where needed
- Implement a build system that can compile against either codebase
**Benefits**:
- Reduced maintenance overhead
- Synchronized bug fixes
- Clearer distinction between shared and unique functionality
- Smaller codebase footprint
The unification would particularly help with:
- Reader protocol implementations
- Server connection handling
- Common utility functions
- Basic ECM/EMM processing
Would appreciate thoughts from both developer communities on this proposal.
---
