| Summary: | scan and Update ebuild | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | INODE64 Sistemas <web> |
| Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | update-ebuild.sh | ||
|
Description
INODE64 Sistemas
2005-11-02 15:17:10 UTC
Created attachment 71963 [details]
update-ebuild.sh
first version of script
Not really sure what the purpose of the script is (haven't actually run it yet), could you provide one or two examples? Don't want to resort to guessing ;) Also from a quick glance I noticed that the config parsing is wrong, you have to account for env overrides and the order in which you source make.conf and make.globals is reversed. More comments once I have a clue what it's for Please reopen once you've provided answers for questions in comment #2 |