On Mon, Jul 25, 2016, at 02:52 PM, Ralf Mardorf wrote: > I tried to do this since years, but didn't find any explanation on how > to do this. >
Did you ever ask for advice on how to dit? The meta is built with the help the tool *germinate*. There's a config file in the source (update.cfg - which needs to be updated for each new release, and hasn't been yet, but I will fix that on next upload). In the config file you will find the url for some seed files. Some of the seeds are the same for all official Ubuntu flavor desktop metas, some are specific for the flavor. So, in order for us to make changes the packages audio, video, graphics, etc, we do that in our seeds - not in the meta itself. Once the seeds have been changed, the meta is updated. If you want to create your own custom meta, you can clone our seeds, and the add your own bzr branch for it in launchpad. Then, also create your PPA to which you will upload your own custom meta. In the config for the meta, change the url so it points to your own seed files. Usually, we only change the codename, but I'm sure you can work out the logic for the renaming. Finally, to create the new meta package (once you have changed the config), you run the update script: fakeroot debian/rules clean ./update dput <somewhere> <changesfile> If you need more info, let me know. This is quite a sparse explanation, but I'm guessing you will make sense of it. If not, just let me know. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
