Friday, November 26, 2010

Promises promises

To share with the pen leaves the messages for others over a longer time and it is less easy to mis-quote that the spoken word. Does everything really deserve to be written? Not in the least. So the intent here is to one day have something helpful to others and perhaps to even profit by the spread of common ideas and interests in some way. Enough to make living easier anyway.To that end this document will be undergoing some changes over time.

Flameeyes wrote Autotools Mythbuster to assist those using the autotools suite of software building tools to configure build and install programs. Being a non-native speaker there were ways I could help to improve it and perhaps help those developers using them and thus improve the distribution Gentoo and software built with it's toolchain since I use Gentoo on several machines.

Recently I pushed some changes I had made in my tree using git. Git is a version control system that allows collaborating authors to work on documents or code and also limit who can make changes Using linux I have as of yet not managed to get any of the graphical interfaces for git to work the way I wish; so the terminal and git is where syncing is done.

In my installation there are 3 branches.
1) 'master'
2) 'to-be-published'
3) 'user99s-to-be-published'.

Recently I did 'git push' from the master branch after a merge and new things went in after the most recent merge request. But I wondered how it was that the merges I had commited were not posted. Still after a year and with the new content that Diego has added the Guide is very good and I am proud to have contributed.

Gentoo QA team has implemented FORTIFY_SOURCE as an option in gcc and on amd64 This tests static sources for problems as software is being built. And should in the end lead to a stable tree for Gentoo that is well checked by development for bugs. This does not address runtime bugs but should limit them in number I would venture. If the QA team has it's way it might be a 'Badge of Honor' that software is considered stable and part of the Portage tree. There is lots of open source code out there. Wouldn't it be a good thing if you knew your software had been checked to the limit of your compiler and the tests development could come up with?

so what could happen? A lot of software could be removed form Portage. There could be a smaller set of packages that had passed Quality Assurance at first anyway. As long as enough tools can pass to have the tools we need as users then upstream bugs should be reported to them and if needed the ebuild masked. Large/stable projects code should have plenty of upstream anyway.

But all bugs should be reported to and tracked by Gentoo if the software is part of the Portage tree.

2 comments:

  1. I'm afraid mostly A-M has been on low priority for me :/

    It's not just your merges that are lingering there, but I really haven't had time to sit, apply merges, and write more about it. My situation here tends to be precarious so a lot of stuff I've been doing keeps being left midway, both regarding Gentoo and other FLOSS work.

    I hope to be able to be more reliable at some point, but it definitely won't be before end of the year :(

    ReplyDelete
  2. Err...I didn't mean you hadn't merged them...but rather my ineptitude with git had left changes in my tree I had thought I pushed already.

    ReplyDelete