Opened 14 years ago
Closed 13 years ago
#8838 closed enhancement (Won't Fix)
win32 build script doesn't update dependent packages (e.g. binutils)
| Reported by: | Owned by: | robertm | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.25 |
| Component: | Packaging | Version: | Master Head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
There seems to be a problem with the dependency handling in the win32 build script. For example, the extraction of the binutils package is based solely on the existence of the binutils.info file. This means that if the dependency is changed to a newer version, it will never be extracted.
Attached is a patch which tries to deal with this. I've added a new cause type of "shell" which allows shell commands to be used as triggers for actions. I've fixed the dependencies for binutils and a few of the others which lent themselves to it.
Attachments (1)
Change History (7)
Changed 14 years ago by
| Attachment: | win32-packager-depfixes.diff added |
|---|
comment:1 Changed 14 years ago by
| Owner: | set to robertm |
|---|---|
| Status: | new → assigned |
comment:2 Changed 14 years ago by
| Status: | assigned → infoneeded |
|---|
comment:3 Changed 14 years ago by
Well, it took a little while, but I've done a complete environment and myth rebuild using the attached patch and it worked for me.
comment:4 Changed 14 years ago by
| Milestone: | unknown → 0.25 |
|---|---|
| Status: | infoneeded → assigned |
| Type: | defect → enhancement |
Note: See
TracTickets for help on using
tickets.
Richard,
Have you run the build script entirely through with these modifications on a fresh build environment? I am anxious about making this drastic a change (and of testing it myself) without some assurance that you've gotten that far with it first. If you can confirm that you have gone for a fresh system, through the script, to a working build, I will do the same. I do think that the aim of the improvements is worthwhile.