| 1 |
On 21-03-2011 12:00:34 +0100, darkdefende@×××××.com wrote: |
| 2 |
> > Have you considered a 100% automatic ebuild generator? Based on |
| 3 |
> > heuristics you can come quite far in generating a first shot. Think of |
| 4 |
> > tools like autoscan, and what brew create[1] for instance do. |
| 5 |
> > |
| 6 |
> Well it would be quite hard to make it 100% automatic as there are so many |
| 7 |
> ways you can unpack->prepare->compile->install. |
| 8 |
> Perhaps it would work for simple makefile projects but then you have scons, |
| 9 |
> cmake, python and java projects. |
| 10 |
|
| 11 |
How hard do you think it would be to detect that you are actually |
| 12 |
dealing with one of those? |
| 13 |
|
| 14 |
> I have no idea how I would automaticly figure out the useflags, deps and |
| 15 |
> the build process without user input! |
| 16 |
|
| 17 |
Of course you can't make it 100% perfect. But would you be happy if you |
| 18 |
could do a fairly good job in 70% of the cases? |
| 19 |
Of course guessing and heuristics are your main tools here, but often |
| 20 |
you find that they are actually right, and hence are reducing the work |
| 21 |
significantly. (And so increading the usefulness with the same amount.) |
| 22 |
|
| 23 |
> > What are the questions you envisage to present the user here? |
| 24 |
> > |
| 25 |
> It won't really be questions prompted to the user but inputfields where |
| 26 |
> you'll write how you would build it normally. |
| 27 |
|
| 28 |
Why do you think a user knows? |
| 29 |
|
| 30 |
> For example in the "How would you build/install" field you would for a |
| 31 |
> simple makefile project type: |
| 32 |
> make && make install |
| 33 |
> And the program should convert that to the corresponding commands in |
| 34 |
> src_compile() and src_install() |
| 35 |
|
| 36 |
I challenge you to think of a way to unpack a tarball, analyse its |
| 37 |
files and then conclude it's aparently a autoconf-based package, so |
| 38 |
configure, make and make install will likely be the way to do it. |
| 39 |
|
| 40 |
> > In general, trying to come up with a use-case (or two) helps to get |
| 41 |
> > yourself a focus on what you would like to do, and what not. A clearly |
| 42 |
> > defined project has multiple advantages for everyone involved. |
| 43 |
> > |
| 44 |
> I thought that this would be to help with generation of small to medium |
| 45 |
> sized projects. But if I have time I will try to make it able to generate |
| 46 |
> a working firefox/blender ebuild ;) |
| 47 |
|
| 48 |
This sounds more like making an example, not a use-case that describes |
| 49 |
how your technique should be used, and why it is really useful/much |
| 50 |
better than the current way of doing things. |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
Fabian Groffen |
| 55 |
Gentoo on a different level |
Archives