a stitch in time: jhbuild
Formal Metadata
| Title | a stitch in time: jhbuild |
|
| Subtitle | staying on top of portability before it becomes a problem |
|
| Title of Series | |
| Number of Parts | 41 |
| Author | |
| License | CC Attribution - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | BSD porters have always struggled with portability of software written by Linux users and never tested elsewhere. GNOME has been particularly difficult. New releases would come with new headaches, every six months. By the time the issues were addressed and fixed upstream, a new release would be out with new issues.
In 2014, the FreeBSD GNOME Project changed their approach. jhbuild is now building the full GNOME stack on FreeBSD systems, at least twice daily, directly out of upstream git master. When portability issues creep in, they are addressed immediately often with patches going upstream the same day. When it comes time to build ports from release tarballs, there are no surprises. A direct result of this effort has been two on-time releases of GNOME (3.12 and 3.14) in FreeBSD and GNOME 3 finally landing in the official ports collection.
This talk will discuss what was done and how it changed the relationship of the FreeBSD and GNOME projects as well as discussing important issues going forward. |
|
