Use a different installer about yori HOT 12 CLOSED

ysetup is a stub installer that downloads the packages you select and installs them. It can't be extracted because it doesn't have a payload.

If you'd like to obtain the raw packages, after performing a core install run "ypm -rl" which will list the URLs of each of the packages on the server. These are compressed using the .cab format, which should be openable in explorer or via the expand.exe command line tool which is included in Windows.

If you want to be able to install from an offline set of packages, see the section on "mirrors" at http://www.malsmith.net/yori/guide/#updating .

from yori.

http://www.malsmith.net/download/?obj%yori/latest-stable/=c:\local\packages\

404 Not Found

from yori.

Quoting the paragraph above that line:

Ypm can also mirror packages, re-routing requests destined to one source to another source. To do this, add a [Mirrors] section in packages.ini with each line containing a value to substitute with another value. The '%' character can be used to indicate an '=' character, which is otherwise inexpressible because it delimits the value to replace with the new value to use. For example, to remap malsmith.net packages to a local location, use:

So that line includes a source URL to map from and a target path to map to, which in this case is "c:\local\packages". "C:\local\packages" is not a server resource, and it is expected that the server would return 404 if it were requested.

from yori.

how to get the raw packages without installing anything?

from yori.

The reason I suggested performing a core install first is to provide a mechanism to query the server to find out what packages it contains. At a pinch you could probably just look at the list from http://www.malsmith.net/download/?obj=yori/latest-stable/pkglist.ini , and assemble the URLs from that. Obviously this is only looking at the latest stable yori release, not anything else the server might host or refer to.

Using ypm -rl is just automating this process into something that's easier to use, easier to support, and more correct.

from yori.

to any interested, here is example URLs:

• http://malsmith.net/download?obj=yori/latest-stable/yori-core-amd64.cab
• http://malsmith.net/download?obj=yori/latest-stable/yori-core-win32.cab

from yori.

Ok, just out of curiosity, I have to ask...

If you trust the binary code, why not run "ypm -rl" to get the full list in a way that will work over time?
If you do not trust the binary code, why would you want to download the binary packages?

from yori.

I trust the packages, but not the installer.

Binary packages are just dumb files, they typically dont do anything beyond their main purpose.

But installers can be nefarious, either intentionally or from lazy coding. They can add registry entries, modify environment variables, add start menu entries.

I dont want any of that at this point, as I dont know if I even like the software. In my case ZIP or CAB file is a simple and more trusted way to test new software.

from yori.

That makes sense, I feel the same way, and ysetup was written in that mindset. If you haven't launched it, this is what it looks like. All the things you're referring to are on the right, optional, and disabled by default:

Also, just checking the source code, ysetup is the only thing in the source tree that interacts with the registry directly. It modifies if the "add to path" options are selected, and queries in order to find the location of Program Files.

from yori.

@malxau nice! thanks for the info! maybe I will give the installer a try, since it is well behaved

I would only add that it might be helpful to link to pkglist.ini in the docs for any who might want manual install

thanks again

from yori.

Obviously there's not really much I can do to make this work nicely without code, but:

• Commit c517bc3 allows ypm to download an entire package set to a local directory
• Commit 3eeeaee allows ysetup to install from a local directory of packages

Note that packages are currently just collections of files; there's no support in ypm for registry changes, shortcut creation, etc. It's just laying out files and installing links to them in an .ini file in the same directory.

from yori.

I dont want any of that at this point, as I dont know if I even like the software. In my case ZIP...

I feel the same.

Is there a reason to not provide a zip with all the utilities, for those who are interested in such thing?

I would guess that you too, when you want to try something which you didn't write, would prefer to get a zip, extract it yourself and try it out in that dir, instead of downloading a downloader which you need to run in order to try the thing, which might change things at the registry etc (even if your tool doesn't, and even if that 3rd party tool also doesn't).

You will not be the first to provide a zipped package without an installer/setup/downloader ;)

from yori.