BROADCASTS.com

Packaging for a distribution means taking sources from upstream\nprojects, applying fixes and modifications, adding some\nconfiguration and then build the result by calling some commands.\n\nRPM formalized the process following a "pristine sources" model. The\napproach is basically to take the unmodified sources as released by\nupstream and store required changes in the form of patches as well\nas a build description next to them.\n\nTimes have changed. The distributed version control system git\ndominates the free software world. Juggling tarballs and manually\napplying patches is no longer a natural workflow. Packager life\ncould be much easier if downstream changes could be applied by means\nof git too, skipping tarballs.\n\nThis talks presents a way how to apply the pristine source idea to a\ngit based world, without history rewriting in the distro repo.\n\nPackaging for a distribution means taking sources from upstream\nprojects, applying fixes and modifications, adding some\nconfiguration and then build the result by calling some commands.\n\nRPM formalized the process following a "pristine sources" model. The\napproach is basically to take the unmodified sources as released by\nupstream and store required changes in the form of patches as well\nas a build description next to them.\n\nTimes have changed. The distributed version control system git\ndominates the free software world. Juggling tarballs and manually\napplying patches is no longer a natural workflow. Packager life\ncould be much easier if downstream changes could be applied by means\nof git too, skipping tarballs.\n\nThis talks presents a way how to apply the pristine source idea to a\ngit based world, without history rewriting in the distro repo.\nabout this event: https://c3voc.de