| 1 |
On 4/29/06, Steve Herber <herber@×××××.com> wrote: |
| 2 |
> > This simply couldn't be automated in a sane manner. There's too much |
| 3 |
> |
| 4 |
> Sane? A crude script that can create an ebuild with just |
| 5 |
> the minimum fields may not work very often, but if it works |
| 6 |
> for the package YOU want, then you have just saved YOUR time. |
| 7 |
> If it partially works, then you are that much closer to testing |
| 8 |
> the package. That extra time could then be used to improve the |
| 9 |
> ebuild and maybe get it working. That seems pretty sane to me. |
| 10 |
|
| 11 |
What would be the difference between having a script to create an |
| 12 |
ebuild, vs a simple template ebuild to start from? The |
| 13 |
/usr/portage/skel.ebuild is all of 17 lines when you ignore comments |
| 14 |
and blank lines. And most of that are package settings for |
| 15 |
dependancies and source locations and the like. Any script that was |
| 16 |
created would have to prompt you for all of that stuff, so running the |
| 17 |
script would be just as 'difficult' as copying and modifying the |
| 18 |
template. |
| 19 |
|
| 20 |
-Richard |
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-amd64@g.o mailing list |
Archives