1 |
Natanael Copa wrote: |
2 |
|
3 |
> On Mon, 2007-10-08 at 06:52 -0700, Alec Warner wrote: |
4 |
>> On 10/8/07, Natanael Copa <natanael.copa@×××××.com> wrote: |
5 |
>> > On Sun, 2007-10-07 at 21:26 -0600, Joe Peterson wrote: |
6 |
>> > > Mike Frysinger wrote: |
7 |
>> > > > Fabian has summed it up nicely, thanks. i could care less what |
8 |
>> > > > your userland is outside of the ebuild environment since it doesnt |
9 |
>> > > > matter to ebuild |
10 |
>> > > > writers. you want a deficient runtime environment, more power to |
11 |
>> > > > you, but |
12 |
>> > > > forcing that environment onto ebuild developers is not acceptable. |
13 |
>> > > > off the top of my head, i'd like to see GNU find/xargs added to the |
14 |
>> > > > ebuild environment. |
15 |
>> > > |
16 |
>> > > Mike, exactly as I said. That's option #2, and I think it could be a |
17 |
>> > > great solution. As for deficient, well, that's in the eye of the |
18 |
>> > > beholder. ;) |
19 |
>> > > |
20 |
++ on the general idea: GNU sed, grep, awk, ed and find get my vote (as well |
21 |
as BASH ofc.) (I don't /think/ you need xargs anymore with find .. -exec.) |
22 |
|
23 |
>> > |
24 |
>> > Question, if you go for #2. Does that mean you will need all the |
25 |
>> > required GNU userland to do binary only installs? |
26 |
>> > |
27 |
>> > It would be highly desireable to be able to do binary installs (write |
28 |
>> > your own binary only package manager) without depending on all the GNU |
29 |
>> > stuff needed to compile the packages. |
30 |
>> |
31 |
Well all you're talking about is BASH and a few others on the machine that |
32 |
builds the binaries afaict. I don't see that as a major imposition. You can |
33 |
then package for downstream using whatever you like. |
34 |
|
35 |
If you're that motivated why not just start hacking on binary support in |
36 |
portage/pkgcore/paludis? There's always open bugs. |
37 |
|
38 |
>> Your own binary only package manager would still need to provide |
39 |
>> Option #2; ie you need to have GNU tools installed to process the |
40 |
>> binary packages. pkg_* functions could still have GNU stuff in them |
41 |
>> and those still get run during a binary package install. |
42 |
> |
43 |
> If we would like to be able to do binary installs without the GNU tools, |
44 |
> what alternatives do we have? |
45 |
> |
46 |
<snip stuff that all takes a lot of effort for zero end-user gain> |
47 |
|
48 |
> Any other alternatives? |
49 |
> |
50 |
> Comments? |
51 |
> |
52 |
I'd just specify BASH (as I don't see the point in making the distinction as |
53 |
it only applies to build machines) and coreutils/findutils etc. |
54 |
Asking everyone to switch coding style for certain functions, just to |
55 |
support the stuff that Gentoo was designed to do from the beginning, seems |
56 |
counter-productive. For every market except embedded, which we've discussed |
57 |
already, BASH is not a major issue: nor are the other tools mentioned. |
58 |
> |
59 |
> Alternative C is what I do today. |
60 |
> |
61 |
Sounds rough :) |
62 |
(I really would recommend #pkgcore as well as there is several years of work |
63 |
to do with binpkgs in that.) |
64 |
|
65 |
Standardising on a certain subset of base GNU tools seems like a good idea |
66 |
to me too. |
67 |
|
68 |
|
69 |
-- |
70 |
gentoo-dev@g.o mailing list |