1 |
On Fri, 21 Dec 2007 03:41:04 +0100 |
2 |
Luca Barbato <lu_zero@g.o> wrote: |
3 |
> Ciaran McCreesh wrote: |
4 |
> > On Fri, 21 Dec 2007 03:17:12 +0100 |
5 |
> > Luca Barbato <lu_zero@g.o> wrote: |
6 |
> >> Putting a tag in the file name or at the to of the file as comment |
7 |
> >> (maybe using a #! line) is the same ... |
8 |
> > |
9 |
> > Three problems: |
10 |
> > |
11 |
> > * We have to wait a year before we can use it. |
12 |
> |
13 |
> We have to wait till we got a new release and I hope it isn't |
14 |
> 12months. |
15 |
|
16 |
No, you have to wait until it's safe to assume that everyone's using a |
17 |
package manager that supports it. |
18 |
|
19 |
> > * It's a format restriction. Some formats have to start with |
20 |
> > something that's not #!. |
21 |
> |
22 |
> if the format doesn't allow anymore the #! comment for then it won't |
23 |
> be an ebuild anymore but an xbuild a ybuild a jbuild or whatever |
24 |
> markup you may propose as alternative to shell like syntax. |
25 |
|
26 |
Mmhmm. And then... Oh, we'd use a new file extension. |
27 |
|
28 |
> > * Ebuilds can't sensibly run in a Unix interpreterish way. |
29 |
> |
30 |
> Would you mind articulate a bit? |
31 |
|
32 |
There's no sensible way for ./blah-1.23.ebuild to work. Ebuilds aren't |
33 |
self-hosting, and a package manager isn't an interpreter, so the #! |
34 |
model doesn't work very well. |
35 |
|
36 |
-- |
37 |
Ciaran McCreesh |