On 3/9/07, Michael Homer <[EMAIL PROTECTED]> wrote:
On 3/9/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > 2007/3/9, Michael Homer <[EMAIL PROTECTED]>: > > Well, hopefully I've fixed all of those. It now uses GetAvailable.conf > > and Compile.conf for everything appropriate, and shouldn't throw the > > errors with Current. That said, though, if you don't have Current set > > to your latest installed version you'll run into trouble when > > something depends on that version and can't find it. > > The MANIFEST.bz2 files are used for binary packages, with the > > addresses taken from GetAvailable.conf - it will only retrieve a > > maximum of one of them, so if they're not mirrors the second and > > subsequent entries miss out. I'm not sure how to deal with that yet, > > or if it's necessary. > It could be nice, since I have my other computers as eachother's > repositories, as I want to use packages compiled at one computer at > (one of) the others. That's probably not uncommon, all things considered. I will make it fetch them all and cat ... | sort -u, figuratively speaking. Do your internal repositories have the dependency files too? Or, are they built straight from the recipes? (i.e. their dependencies are always the same as the same-version recipe) > I do miss the legend as well, explaining what IUR means. Freshen --help gives that. Installed/Upgrade/Recipe(Binary, X=both available). They're not terribly useful, since downgrades are pretty much nonexistent and non-Installed is rare. > > A feature that I think would be nice is to see why an application is > in the list, i.e. what application that had that dependency. Good idea. I will add that, possibly for the release after this one since it may not be simple.I'm actually not sure how well the addition of uninstalled dependencies to the tree is working - it's more of a happy accident of the sorting algorithm than by design at this point. If you notice any bugs with it let me know. In particular, I've just realised that I don't think their own dependencies are included in the calculations. > > It will also terminate immediately a Compile or InstallPackage fails. > > Compile/InstallPackage -U isn't used yet since there isn't a Compile > > or Scripts release with them in it yet, but the ability is there to > > enable it. > > > Perhaps an option to Freshen to enable them anyway? > Anyhow, there will be a Scripts/Compile release soon as there is a bug > with signing and verifying packages. You can edit it to add them for your own use - lines 344 and 358 of the main script for Compile and InstallPackage respectively. Or: sed -e 's/#{sudo} Compile/#{sudo} Compile -U/; s/#{sudo} InstallPackage/#{sudo} InstallPackage -U/;' Freshen > new-Freshen && mv new-Freshen Freshen It will batch all the UpdateSettings calls at the end, for the moment. I will add an option to disable them entirely, and one to inline them. > > Version 2.0.99 is attached, and signed this time. It will be necessary > > to update Freshen.conf, since a lot of fields have been dropped in > > favour of their companions in GetAvailable.conf and Compile.conf, and > > one has been created. The default settings should be fine for > > everybody, since the bulk of the ones you'd want to change are now in > > the system config. > > There's a bug in signing and verifying signaatures in the latest > version of Scripts, so I can't verify this package. > But what I can say is that you have left the backup of Freshen.conf in > the default settings directory. And the backup of Freshen, too. Good catch. The system I'm doing development on isn't my home system, so I won't be able to act on any of these or roll a new package until Monday. Hopefully the new scripts will be out by then so I can have that enabled by default.
Ok. So I've done pretty much all of that, tested it, it all seems to be functioning. If there are no major problems, I'll tag this as 2.1 final and get a recipe out as well. Changes since the last release: - Bug fixes in the version code that made it miss some programs. The upgrades list will gain and lose some items because of that. - As a result of that, the U flags in the updates list now works as expected. There's also a new "N" flag for new (i.e. not installed) programs. - It now uses the -U flags to Compile/InstallPackage, and as a result requires the newest release. - Uninstalled dependencies will now be properly added to the tree, along with their dependencies - You can get a list of what depends on program X with "Freshen --info X", provided you're at "verbose" level or above (which is the default, or -V enables it). I will consider adding a full tree display if anybody wants it. The reason it only does it at verbose and up is that it has to calculate the updates list to do it, and that may not be desired every time. - There is a configuration option to fetch every packages manifest and merge them. Package attached. Configuration file change is the addition of the fetchAllPackageLists option. By the way, in creating the package I got a pile of errors in this form: /Programs/Scripts/2.6.3/bin/../Functions/File: line 130: /Programs/Freshen/2.0.999/Resources/FileHash: Permission denied `sudo CreatePackage` did not help. So the package is not signed, so it probably needs a manual SymlinkProgram after installation. It seems from looking in Functions/File that that would mean packages can only be created as root, since $hashfile will never be world-writable. `| $sudo_exec tee -a "$hashfile" > /dev/null`? -Michael
Freshen--2.0.999--i686.tar.bz2
Description: BZip2 compressed data
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
