| Summary: | unpack "${A}" doesn't work for more than one file in SRC_URI | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Alexandru Toma <flash3001> |
| Component: | Documentation | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
document what exactly ? you're talking about basic shell coding here, the fact that it's ${A} is irrelevant
ebuild manpage says `unpack` takes a list of sources ... ${A} is a list of sources, but doing "${A}" means pass everything in ${A} as a single argument
Yes I figured that out by myself. However, some people might still be confused by this before they realize what's going on. Usually you use quotes around the variables in an ebuild so the natural instinct is to use quotes here as well to make everything neat. Yes, I should have realized sooner (this is not my first ebuild after all) that by putting quotes around ${A} I turned it into a string, but I still made this mistake. I was just thinking that other people might also get a little confused so mentioning something about this would be a good idea, but that was just a thought... you can do as you wish.
k |
I was trying to write an ebuild and noticed that unpack "${A}" doesn't work (for more than one file in SRC_URI) ... the correct syntax seems to be unpack ${A} (without the quotes). This is not documented anywhere (I couldn't find it at least) and I think it should be mentioned somewhere. I became very frustrated while writing the ebuild because I couldn't understand what was going on. Having this mentioned in the docs somewhere would be helpful I think. It should definately be mentioned in "man 5 ebuild", because for me, and many others I think, that's the first place I look when I don't remember something or something doesn't work.