On Fri, Aug 9, 2013 at 12:14 AM, Александр Соколов <[email protected]> wrote: > We forget about maintainers. Shared repository complicate the creation of > ebuilds and PKGBUILDs. > > Of cose we can make a separate repository like lxqt-sdk, it will contain a > some scripts to facilitate the lifo of the developers (like checkLicense.sh > and astyle-razorqt.sh). Also we can put the script clone-and-build-all. But > this repository should be optional. > > 2013/8/8 Ben <[email protected]> >> >> On 8 August 2013 22:48, Jerome Leclanche <[email protected]> wrote: >> > >> > >> > On Thu, Aug 8, 2013 at 7:18 AM, [email protected] >> > <[email protected]> wrote: >> >> >> >> >> >> 2013/8/7 Александр Соколов <[email protected]> >> >>> >> >>> To have common repo is not a good idea. User should to have ability to >> >>> clone repo and build application, without any additional steps. But if >> >>> we >> >>> have several related repositories, for building user must to create >> >>> directory structure with predefined names, and clone the repositories >> >>> in >> >>> them. >> >>> >> >> >> >> I don't think having a common repo for build tools is worse than having >> >> a >> >> common library you need to build and run the modules. And I think there >> >> is a >> >> difference between what goes into the library (all users of lxqt need >> >> this) >> >> and what goes into the build-tool-repo (lxqt developers need this). >> >> >> >> But I can live with putting everything common in a library module, if >> >> people prefer this. >> > >> > >> > Don't really see the point. Build tools are just build tools; they >> > should go >> > in the main repo and be used to bootstrap everything, imho. They're here >> > to >> > help developers, we don't distribute them to users... arguing over it is >> > just going to waste the time we'd save with them ;) >> >> Then what's the point of having separate repos for each lib or >> application, if they are not buildable on their own? >> >> As downstream packager I'd really appreciate it if each repo/lib/app >> had its own makefiles, without needing to bootstrap anything else. >> >> Cheers, >> >> Ben | yngwin >> Gentoo developer
> Best regards, > Alexander. I think the solution is easy. Create a repo which contains the latest razor cmake modules and scripts. For every component, just copy the required cmake modules. That's what I did with libsysstat. It now can be built independently. https://github.com/lxde/libsysstat As you can see, it only uses create_pkgconfig_file.cmake and don't need other modules. The only drawback is, if we improve some cmake modules later, the other copies in every repos will be out of sync. This is a rare case, though, and it's still easy to fix. Just using the find command to find out all repo using that cmake module, and copy the latest version to them. They don't necessarily need the new cmake module if they already work well, though. So I see no problems here. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
