1 |
I want to use ebuilds, versus tar, so I can easily remove the package when |
2 |
I am done with it. |
3 |
|
4 |
Your wizard script would be version 0.1 of the script I want to end up with. |
5 |
|
6 |
Thanks, |
7 |
|
8 |
Steve Herber herber@×××××.com work: 206-221-7262 |
9 |
Security Engineer, UW Medicine, IT Services home: 425-454-2399 |
10 |
|
11 |
On Sun, 30 Apr 2006, Duncan wrote: |
12 |
|
13 |
> Richard Fish posted |
14 |
> <7573e9640604301028k6e46acd0tc73cde05e0aaf183@××××××××××.com>, excerpted |
15 |
> below, on Sun, 30 Apr 2006 10:28:23 -0700: |
16 |
> |
17 |
>> What would be the difference between having a script to create an |
18 |
>> ebuild, vs a simple template ebuild to start from? The |
19 |
>> /usr/portage/skel.ebuild is all of 17 lines when you ignore comments |
20 |
>> and blank lines. And most of that are package settings for |
21 |
>> dependancies and source locations and the like. Any script that was |
22 |
>> created would have to prompt you for all of that stuff, so running the |
23 |
>> script would be just as 'difficult' as copying and modifying the |
24 |
>> template. |
25 |
> |
26 |
> A script that prompted for all that and used the answers to write a simple |
27 |
> ebuild wouldn't be so bad. However, it would actually be /more/ work than |
28 |
> simply compiling and installing from tarball, so if the object was a quick |
29 |
> install of the package, it wouldn't be worth it. OTOH, a simple ebuild |
30 |
> generation "wizard" script/applet might be worthwhile in its own right. |
31 |
> |
32 |
> -- |
33 |
> Duncan - List replies preferred. No HTML msgs. |
34 |
> "Every nonfree program has a lord, a master -- |
35 |
> and if you use the program, he is your master." Richard Stallman in |
36 |
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
37 |
> |
38 |
> |
39 |
> -- |
40 |
> gentoo-amd64@g.o mailing list |
41 |
> |
42 |
-- |
43 |
gentoo-amd64@g.o mailing list |