On Wed, 27 Feb 2013 12:19:39 +0000 Daniel Willmann <d.willm...@samsung.com> wrote:
> On 27/02/13 12:05, David Seikel wrote: > > On Wed, 27 Feb 2013 11:51:11 +0000 Daniel Willmann > > <d.willm...@samsung.com> wrote: > > >> Sounds pretty clear to me - am I missing something? > > > > Yes, you are missing the "automatic" part. If there's no > > "automatic", then the list is subject to human error, or bad > > judgement, or both. "Automatic" means everything is in the list, so > > individuals can choose what is important to them. > > > > That list is automatic though, so one step closer to fully automated > > scripts. B-) > > I understand though I would still disagree that this is something > desirable. The automated scripts will still not tell you which of the > repos you actually need, how the deps are, etc. It's all part of automating build scripts. It's not everything, but it's a useful part. The point is to know where to look for the repos that are needed. I spent a lot of time helping Morlenxus with his easy_e17.sh script. With the new GIT repos, there was gonna have to be major surgery on that script, and I was thinking that it was already way more complex than what I need. So I wrote one from scratch, more suited to my own needs, and way simpler. There's lots of other build scripts around to, most are way less complex than easy_e17.sh. Then again, most are made just to suit the needs of the developer that wrote them. Easy_e17.sh is very complex coz it caters for the needs of as many people as Morlenxus could handle. One thing that was a pain was always having to update easy_e17.sh each time something new came along, got moved, a new dependency, or a new build order. And each time it had to be updated like that, we had to worry about lots of people still using old versions complaining that it no longer worked. Since lots of people used easy_e17.sh, there was also increased support load on the rest of the Enlightenment developers. Sooo, my new build script will try to automate as much as possible, to keep the changes needed down to a bare minimum. The more clever the build script is, the less work has to be done to update it to cater to changes. This is what lazy, good for nothing coders do, work hard on their code so they can be lazy later. In this case, it's better to be able to get the structure of the repos automatically than to keep updating the script. Both easy_e17.sh and my new script already automatically searched SVN for the projects to build, and automatically figured out how to build them. Now my script can do similar searching in GIT using this file you have exposed on the web site. Morlenxus might update easy_e17.sh to do the same before I do. A future step is to figure out the deps. Luckily most of the dependency issues went away when we merged libraries into the EFL tree. The rest I would be OK with hard coding into my script for now. In the end though, it's a problem all build scripts have to solve, so it might be good to have that info in the repos somehow. Perhaps any project that has a dependency from the Enlightenment repos could include a e_deps file that simply lists them, one per line? That's something to think about in the future though. In the end I want my script to be clever enough that I can simply say "I want e, efbb, rage, and terminology" and the script figures out the rest by itself, without anyone having to constantly update it with new info. Morlenxus might want this to. As soon as I asked for this list of repos, other people asked for it to, apparently for the same reason. Actually, I think I'll teach my script about the basic deps (everything depends on efl, so build that first; this, that, and the other depends on elementary; plus a few more), then list the things I really use in the proper build order. Then I can just add a few loops to scan SVN and GIT, to build the left overs. Yes, I DO try to build almost everything. B-) > But okay, agree to disagree here. :-) I can handle that. I can't handle rude people telling me I don't want things I just said I want. Thanks for being more understanding. > I'll check if I we can expose the repository list that gitolite > generates for cgit to parse - I guess that would help you. It's working well. I'll be comitting changes to my build script later tonight once I'm done. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel