On Tue, May 18, 2010 at 10:43 AM, Carsten Munk <[email protected]> wrote: > Hi, > > I've set up http://gitorious.org/meego-device-adaptation and was asked > to populate this with repositories in > http://bugs.meego.com/show_bug.cgi?id=1845 before we hand it over > under project auspices (meego.gitorious.org) > > I propose using naming convention of n900_packagename for the > repositories since we currently can't do subprojects/tagging. Bad/good > idea?
I think this is generally a good idea to get device specific packages together. However I'm not sure if it should be nokia_n900_packagename, as there might be packages related to all of the Nokia devices at some point? Is it easy to rename packages later, i.e., changing the prefix? > > Now, we have the following packages in devel:devices:n900. Could you > if you feel responsible for One or more packages, mail back and tell > which you are. Then your task will be after repository creation to > upload the current packaging to the repository. I think I'm responsible of packaging these: libmlocknice nokia-n900-configs nokia-n900-rescue-initrd nokia-usb-networking udev-rules-nokia-n900 i2c-tools > > camera-firmware > fb_text2screen > libdsme > libmlocknice > nokia-n900-configs > nokia-n900-rescue-initrd > nokia-usb-networking > udev-rules-nokia-n900 > i2c-tools > > Also, are we missing any more packaging that could be in the open like this? I think those are all of the packages currently. > > Hint: adding .osc to .gitignore is a big help. To make a package into > a git repo, git init, add .osc to .gitignore, git add ., git commit -m > "Initial commit", then push to gitorious/ > > From the moment you upload this to git, it should be maintained there > and the package description in OBS will reflect this. After that, > package submitreq's to devel:devices:n900 which are not reflected in > gitorious will not be accepted. > > This is in order to aid non-team member contribution as they cannot > currently do package submitreqs nor is there a near-future ability to > do so from community OBS. Fair enough. Will .spec and .changes files be also in the git? If so to which directory should those be put, to package root? And then will those be included to the .tar.bz2 in the future? Or do we put the code to some src directory or something like that? > > Regards, > Carsten Munk > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > Regards, Marko _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
