Have you ever modified the source code of an open source application?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Have you ever modified the source code of an open source application?
I once wanted to modify the sources of the XED text editor because I wanted to disable 'search as you type'. It makes searching very large files impossible because as soon as you type the first character of the search string, the editor begins to mark every instance of that character. This takes ages (sometimes more than a few minutes) and while this is ongoing, it is not possible to enter any additional characters.
But to my surprise I couldn't find anything in the source code to change this. I guess it is a default of the GTK framework used to build the editor.
Yes, I maintain a few patches for FLOSS programs that are unmaintained, but still work fine after patching.
Come to think of it, I also have 1 or 2 for programs that are maintained because I don't like part of the functionality.
I had to do some hacking to make this code build. I didn't actually modify the program itself, so much as hack the make file to make it actually detect the third-party *.h files it needed to finally produce a build. IDK if that counts, since I didn't actually change the C code, just added some -I arguments to the compiler.
Hacking the build system defiantly counts. Without working build systems you'd have no FLOSS programs -- or at least none that could be built with any regularity.
They did not ask if it was for Android, just if it was open source.
Granted, I would have used FLOSS in the question, had I worded it but I didn't write it.
a.) One of the challenges of upstream packaged products is that they come with a built-in selection of options for the software in question. That works well for most people most of the time, but doesn't work well if you need a non-standard set of attributes.
b.) Less often to accomodate builds with non-Linux compilers (esp. those not freely available or for non-Intel CPUs) ... there are variations (sometimes subtle, sometimes not subtle) in compiler flags if you're not using GCC.)
Back when the Freevo DVR project was still active. I hacked the record command, so it would record from a Hauppauge HD PVR. It worked very well for several years thereafter.
I have never "modified the source code of an open source application".
BUT....
..... I HAVE programmed in Basic, Pascal, C, DOS, Unix/Linux Shell, SQL, MS Access, Python.
..... I HAVE used graphical code debuggers that trace the code execution visually line by line, loop by loop.
..... I HAVE compiled code into applications for use on different systems
sooOOoo .... what difference does it make if it's 'Open source applications' ?
Am I missing something here?
Just curious.
It's a very different kind of business. If you are the sole programmer of a program you (should) understand everything and know where to go whe fixing a bug or adding a feature. On the other hand, if you contribute to a project that other people have worked on, you need to figure out things before ever trying to modify the source, which is more time consuming and involves asking questions on the mailing lists, reading/searching for earlier bug reports, understanding how the code evolved to its current state by reading the commit logs and blames...
Yes modified a whole lot of them, but previously; hex edited various binaries, manually modified boot sectors, repacked BIOS images, rewrote some very small assembly stuff, etc.
Must say that after all those low level adventures, reading and editing well documented and clean C/C++ projects has been much more enjoyable experience.
I suppose systems were always more interesting to me so I never really bothered with application coding, especially not java.
You know some old executables are hardcoded to load unavailable resources, like servers which aren't there anymore?
So the kind of edits that make unconfigurable things configurable, I guess. Why?
"Asking for a friend" would be a nice excuse for my ignorance. I have never had the idea to do that, but it's good to know in case I get stucked too. I wonder if I could hexedit those old flash games I downloaded which require to be run from their original website
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.