3 ms·
1. Ability to recompile packages with setting some flags. (make.conf from bsd / gentoo). Example use case - I am investigating a hard to track issue and would
by dman 10y ago
1. Ability to recompile packages with setting some flags. (make.conf from bsd / gentoo). Example use case - I am investigating a hard to track issue and would like to run some system packages with address sanitizer.
2. Ability to easily patch / hack an installed package. Example use case - lets say I want to change my installed ruby runtime to fix a small bug / add some instrumentation.
3. Ability to have my local software be available as a package. Example use case - Have automated tooling to take a CMake based library / executable project and have it be built as an installable rpm package.
4. C++ is changing fairly rapidly currently, having gcc / clang trunk available as a package would allow more users to try out cutting edge features.
5. Having a performant / good looking GDB frontend. Something like DDD for the modern era.
I fully appreciate that one or more of those might be possible today, but it would be nice if the barrier to entry to do these things would be lowered via some tooling / tutorial style documentation.
- mattdm 10y agoLike you say, these are all possible today (with the exception of #5, I'm afraid!) but with a lot of hoops. I'm not sure if the recompile/patch of system libraries is a general enough need to make really slick tooling something we can invest in, but better documentation is certainly possible.