|
From: Chris F. <cd...@fo...> - 2011-09-01 05:21:39
|
On Fri, Aug 26, 2011 at 12:02:46PM -0300, Luiz Angelo Daros de Luca wrote: > Hello Chris, > > I just got a cellphone (and now I can play again with opensync). It is > a simple samsung C3200 that does not work > with any tool under linux. :-) Looks like you'll be doing some opensync hacking then. :-) > I saw that binary-meta now has more interesting make options. Yep, they are being added, slowly but surely. > I tried "make fetch" from a clean git > and got this error: > > (...) > Receiving objects: 100% (747/747), 211.94 KiB | 93 KiB/s, done. > Resolving deltas: 100% (539/539), done. > Submodule path 'sources/kdepim': checked out > '8a793cfb5e07a6f7443cdd00d8de18cdf0bf1b5c' > fatal: destination path 'sources/opensync' already exists and is not > an empty directory. > Clone of 'git://repo.or.cz/opensync/opensync-cdf.git' into submodule > path 'sources/opensync' failed > make: ** [fetch] Erro 1 The only way a build/ directory should show up in the sources/opensync tree is if you did a 'make src' earlier. I'm not sure why git would have failed there. But you can clean your tree with a 'make clean' as well. This uses 'git clean -xdf' in each submodule, and 'git clean -xdff' in the root, to do the cleaning. So changes you make to files that git knows about will stay... but files that git does _not_ know about will be lost, so use caution. You may want to play around with it to see what it does. :-) Just remember that there are basically 3 different modes: src - just builds the code and installs it inside the tree debian packages - deb files show up under debian/ rpm packages - rpm files show up under ~/rpmbuild/RPMS The RPM support is lagging behind the debian support at the moment. - Chris |