Re: NewVersion
"Lucas C. Villa Real" <[email protected]>
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <CAAvzgtZEpQp42HKUUmoFuZHY7_nqDXQ69RtgurGpkYMHZ7_HdQ@mail.gmail.com> |
On Thu, Mar 31, 2016 at 7:06 PM, Hugo Barrocas <[email protected]> wrote: > I've been updating some recipes for Gobolinux 015, and noticed two > small details. > > when we do: > NewVersion (Program_name) (version_number) (link_to_file) > > It creates the new recipe as expected, but the new recipe file never > updates the info: > compile_version=2.0 > > If the previous version was compile_version=1.3, it stays that way. > Shouldn't it update that info to the version we have when making the > recipe? > > No, because compile_version determines which version of Compile one needs to have to parse the declarations in the Recipe. If an older version of Compile (e.g., 1.3) was able to recognize all keywords in the former version of the Recipe, then that same version of Compile should be able to recognize the keywords in the new version of that recipe (because NewVersion does not change anything besides the url and the md5sum). I've also noticed that when compiling the new programs (to test the > recipe) the Dependencies file is not always correctly updated. > Some dependencies are left out and have to be manually inserted. > If the recipe is uploaded without those missing dependencies, another > user trying to install it will fail to compile. > It is hard to detect dependencies automatically. We try to automate it by extracting explicit dependencies from the executable files through objdump. Let me know if you have a different approach that could improve that. Best regards, Lucas _______________________________________________ gobolinux-users mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-users