Re: Team packages maintained in bzr, one branch for the team or one for each debian directory?
On Sat, 2007-07-28 at 17:28 +0200, Sebastien Bacher wrote: > Hi, > > We are looking at maintaining the ubuntu-desktop packages in bzr. The > idea is to store the debian directories there and to use > bzr-buildpackage and some other tools making the work easier. > > There is a question though, which is to know if we should better use one > branch by package or one for everything. I'm trying to summarize some > advantages and inconveniences of each method: > > * One branch by package: > + that's the "clean" way using bzr > + you can checkout and look at updates for the packages you are > interested in only > - you need to checkout or update ~100 different branches when you work > on all the packages > - you need to branch for every package when gutsy+1 opens > > * One branch for all the packages: > + you only need one command to branch, get or update the team packaging > sources > + easier to look if something changed > - you need to checkout the debian directories for all the packages > (quite small) > > The team contributors are likely to work on different packages and I > think it would be easier to have everything at the same location. > > Daniel has written a "get-branches" tool to make easy to get or update > all the branches from a team, it has to connect and do checkout for > every package though which is quite slow and quite verbose. > > > What do you think? What method would you like better? Extra arguments > and thoughs are welcome! > > > Thanks, > > Sebastien Bacher > > > How about dividing the branches into categories with packages split into different subdirs. Many closely related packages are all changed at the same time and therefore should not be in different branches. To combine them all in one branch sounds like a good idea, but maintaining it might be a nightmare. To track all changes made to such an all encompassing branch would be very difficult. Off to-pic a bit, as far as I know bzr does not allow sub branches with different access rules, could be useful. signature.asc Description: This is a digitally signed message part -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Metacity without edge resistance - Help!
On Sun, 2007-07-01 at 11:49 +0200, Andrea Martelli wrote: > Hi, > I'm an Ubuntu Feisty user and I'm trying to create a .deb package from > Metacity 2.18.2-0ubuntu1.1 source, with the file src/edge-resistance.c > modified in order to have no edge resistance: > > const int PIXEL_DISTANCE_THRESHOLD_TOWARDS_WINDOW= 0; > const int PIXEL_DISTANCE_THRESHOLD_AWAYFROM_WINDOW = 0; > const int PIXEL_DISTANCE_THRESHOLD_TOWARDS_XINERAMA = 0; > const int PIXEL_DISTANCE_THRESHOLD_AWAYFROM_XINERAMA = 0; > const int PIXEL_DISTANCE_THRESHOLD_TOWARDS_SCREEN= 0; > const int PIXEL_DISTANCE_THRESHOLD_AWAYFROM_SCREEN = 0; > const int TIMEOUT_RESISTANCE_LENGTH_MS_WINDOW = 0; > const int TIMEOUT_RESISTANCE_LENGTH_MS_XINERAMA = 0; > const int TIMEOUT_RESISTANCE_LENGTH_MS_SCREEN = 0; > > I used the debian patch found on > https://launchpad.net/ubuntu/+source/metacity/1:2.18.2-0ubuntu1.1, but > once generated the package with checkinstall, I'm unable to install it > because of this error: > > overwriting of `/usr/lib/libgconf2-4/2/libgconfbackend-xml.so', which > belongs also to package libgconf2-4 > > Can you help me to obtain a working metacity package with no > edge-resistance, please? > > Thanks a lot, > Andrew Andrew Part of your problem is that you seem to be trying to use checkinstall with a debsrc. While this can usually be done, if the package is already in deb format and ready for use with debbuild or dpkg-buildpackage you would be better off using one of those. Unless you are going to make sure to clean up the mess that checkinstall will make of the resulting deb so that your dpkg and apt will handle it properly you should try using the "dpkg-buildpackage -us -uc -b" command to build changes unsigned sources into binary a deb for your arch. It really is none of my business what you do with your software, but can't you turn off edge resistance in a config file and/or a gui config? -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
