On Tue, Dec 13, 2005 at 07:30:00AM +0100, neoclust wrote: > Le Mardi 13 Décembre 2005 00:16, Julien Gilli a écrit : > > Hello, > > > > neoclust wrote: > > >i am trying to make a rpm of openwengo > > > > For which distro ? > yes mandriva > > Giallu, thl and warren on #openwengo have started to > > work on inclusion into fedora extras. > so i will be able to see there packages on fedora extra cvs mailing list, and > why not use pieces of there spec to have a more unified spec. > > > I think that you probably want to > > create a Mandriva package, but i rather ask in order not to duplicate > > any work. > duplicate ? why ? > > > In any case, your contribution will be very much apreciated. > > this software need to be on all distro, if it works very well maybe we can > hope it replace skype and could be installed by default :) > > > > > >The svn checkout is nearly 123 MB with the most of libs we don't need on > > > linux because already provided by our distro > > > > You're right. Some libraries that are present in the source tree haven't > > been modified yet, so we would be able to take them out of the tree > > without too many changes to the whole source code. However, we have > > changed some other libraries (e.g, curl) so we need to be careful when > > removing them. > > > > >Maybe be a option in scons would be good to avoid this problems. > > > > For libraries that we have modified, there are several ways to take them > > out of the tree : > > - generate a patch that makes a vanilla libs into a customized one, and > > apply this patch to a given release of the lib when we build the software. > > - submit the patch upstream to request its inclusion in the lib. > > > > The best solution, IMHO, is the second one, but it won't always be > > possible. The first one requires that we track each lib's so that we can > > generate a patch that applies blissfully to any new release. > > i think too that the second way is the better,
I personally highly prefer the first solution. If you knew what modifications we make to the third-party libraries we integrate, you wouldn't even ask ;) All our modifications wouldn't interest the authors of the project because they are sometimes hacks, sometimes diffs to work around the project limitations (for example with curl, we added just one function to be able to use curl with an already opened socket). > > > >Curl is provided by the svn checkout but w/o libcurl-devel from my distro > > > it doesn't compile, > > > > I do not have curl--devel package installed, and it builds fine. Could > > you please paste the relevant output of the scons command you used to > > build the software ? > > > > All the best, > > i will try to give you this output when i will retry to compile, because i > have not writed the previous ones :/ > > _______________________________________________ > Wengophone-devel mailing list > [email protected] > http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- David Ferlier -- [EMAIL PROTECTED] "Humor is mankind's greatest blessing." -- Mark Twain _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
