/hydrus/ - when

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1448732454062.png (26.99 KB, 357x75, 119:25, nugetlogo[1].png)

Anonymous 11/28/15 (Sat) 17:40:54 No.1511

when

Anonymous 11/29/15 (Sun) 06:23:19 No.1512

I'd ask the same thing if OneGet actually supported updating. Thanks Microsoft.

Anonymous 11/30/15 (Mon) 02:28:36 No.1514

linux package managers m8

Anonymous 11/30/15 (Mon) 03:11:59 No.1515

>>1512

Oh shit never mind.

https://github.com/OneGet/oneget/commit/bd718d3fd43387d31101b7140a9d271ddfdb4bf1

>>1514

OP is asking when Windows builds will be pushed to Windows package managers such as chocolatey. I can't look right now but if there's one in the Arch AUR that could be used for the Windows version of pacman, same for pkg-src, etc.

hydrus_dev ## Board Owner 11/30/15 (Mon) 18:32:42 No.1519

File: 1448908368532.jpg (288.61 KB, 1065x749, 1065:749, 0c2a545b8bd4b4a43caaaa7f9a….jpg)

I am not very familiar with package managers–I don't know the differences between the different flavours, and I don't have any experience in writing and maintaining a package. If anyone has a particular favourite flavour of manager and does have experience and enthusiasm, please feel free to package my releases however you like, and if there is something I can do to make that task easier for you, let me know.

I currently make my builds with hacked-together batch files and scripts that rely on my personal directory structures, but I plan to migrate to a more open and multiplatform solution, probably something with a setup.py, however that is best generated, in the future.

Anonymous 12/02/15 (Wed) 14:05:38 No.1522

>>1512

A fellow one-get user

nice

I'm not that familiar with powershell scripts, but this won't be in the vanilla windows installation until a new build correct?

Anonymous 12/02/15 (Wed) 14:15:15 No.1523

File: 1449065715468.gif (725.29 KB, 200x197, 200:197, 6243b8a8402951648e162f3042….gif)

>>1519

should have added this to 1522, oh well

The way I think it works is that it downloads the install executable or familiar and runs an autohotkey script (how it's worked for me with programs such as speccy, firefox, sharex)

question is who wants to be the maintainer?

does code tags work here?

$packageName = 'sharex'
$installerType = 'EXE'
$url = 'https://github.com/ShareX/ShareX/releases/download/v10.4.0/ShareX-10.4.0-setup.exe'
$url64 = $url
$silentArgs = '/sp /silent /norestart' # "/s /S /q /Q /quiet /silent /SILENT /VERYSILENT"
$validExitCodes = @(0)
 
Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" "$url" "$url64"  -validExitCodes $validExitCodes

here's the ps1 script for sharex's latest version

with proper automation, it should be relatively easy to set up

hydrus_dev ## Board Owner 12/02/15 (Wed) 22:04:55 No.1524

File: 1449093895627.jpg (102.3 KB, 885x1312, 885:1312, e0145d0bee189c744b7d31c805….jpg)

>>1523

This is neat! If it is any help, I use Inno for my installer, which should work with /SILENT (installs with default options, throws up window to show progress) or /VERYSILENT (installs with default options in the background).

I also plan to add auto-update from inside the program in the future.

Anonymous 12/02/15 (Wed) 22:06:41 No.1525

I'd advise chocolatey over oneget, however chocolatey is understaffed and updates will be stuck in the moderation queue for months at a time.

Just wait until chocolatey sorts out their process.

Anonymous 12/04/15 (Fri) 16:50:46 No.1535

>>1525

Uhh

Oneget is just a module that acts as a a unification if many different package managers, including chocolatey and nuget

It's 4am here, might see if it's worth trying myself

Anonymous 12/05/15 (Sat) 06:46:26 No.1538

>>1522

Correct, even then though it depends on how they update their modules. It could be included in a Windows Update update. Hopefully this addition will allow OneGet to update via OneGet.

>>1525

As >>1535 said, OneGet is just a "package manager manager" with a reference implementation of Chocolatey's manager and some of MS's (nuget). It's essentially a wrapper meant to be used as a common interface between different package managers and repositories. I really like the idea since then you could for instance update you OS with your OS package manager, your third party applications with their package manager(s) (like Chocolatey), and things like Python libraries via pip, but all from the same interface, so you'd do "OneGet Update" and update everything that can be updated without having to call them all yourself. That's the idea anyway, it's not exactly that useful at the moment.

As long as it gets added to some repo somewhere OneGet users should be able to get it somehow, Chocolatey's repo would be the best option for right now and probably forever unless MS themselves decide to host a repo.

Anonymous 12/05/15 (Sat) 12:59:57 No.1540

File: 1449320397612.png (11.46 KB, 797x402, 797:402, 15-12-05_23-58-46.png)

fuuuuuuun….

Anonymous 12/28/15 (Mon) 02:39:45 No.1653

Okay, I'm trying to make a package for HN.

I'm still learning but I made this repo so you can help me if I shit the bed.

*IT IS NOT WORKING YET*

https://github.com/HASJ/hydrusnetworkchocopkg/tree/master

Anonymous 12/28/15 (Mon) 04:13:51 No.1655

>>1653

installation is now working.

gonna start reading on the uninstaller and upgrading stuff tomorrow.

Anonymous 12/29/15 (Tue) 06:20:09 No.1663

https://chocolatey.org/packages/hydrus-network/

Chocolatey moderates each package version so it will always lag at least a day behind hydrus releases, unless I get "trusted status" (not likely anytime soon).

Anonymous 12/31/15 (Thu) 06:22:40 No.1676

>>1663

You can manually install chocolatey packages that are in moderation by specifying the version.

cinst hydrus-network –version 188.0

Will grab 188 even though it has yet to be "approved".

At this time, chocolatey doesn't support versions without decimals, so every hydrus release on chocolatey will have .0 at the end.

Anonymous 01/02/16 (Sat) 04:29:14 No.1684

File: 1451708955915.png (12.51 KB, 1071x436, 1071:436, 16-01-02_15-27-45-Windows_….png)

>>1512

one-get will get, once new versions are approved

I wonder if it's possible to insert the back catalogue of versions

Anonymous 01/02/16 (Sat) 11:35:38 No.1687

>>1684

OK, I did some reading on OneGet, and experimented a little- my initial assessment of "use chocolatey over oneget" still stands until further notice.

OneGet has an extremely basic implementation of chocolatey written by OneGet devs and NOT chocolatey devs, used to install chocolatey packages. They did this because chocolatey is all powershell, but the devs plan to do a C# rewrite. OneGet can't easily support the powershell scripts, so OneGet wrote a basic chocolatey implementation in C# until the chocolatey devs finishes their own official C# release. OneGet's basic implementation…

-does not have proper error handling (example: packages that failed to install will show up as installed).

-does not do things exactly the same way as chocolatey does, so there's a chance things could go wrong (batch redirect vs shim, for one).

-does not, as far as I know, get regularly updated. Chocolatey recently added some new features and is weeks away from releasing more. If an install script uses these new features, chances are OneGet won't be able to run them properly.

-does not bundle 7za, which chocolatey does, and a number of packages take that for granted (example: mpv is released in .7z, but an official chocolatey function wraps 7za.exe so I don't need to have my install script download 7za or have the package call 7z as a dependency. Since OneGet doesn't have 7za.exe, it can't install that package).

Also, as someone mentioned above, OneGet doesn't seem to have the ability to check for updates yet.

The chocolatey devs are rewriting chocolatey in C#. When that gets released, all of the above will be fixed. Until then, if you're making heavy use of the chocolatey repo, you should really be using chocolatey's client. You can install chocolatey through OneGet (Install-Package chocolatey), and chocolatey updates itself.

That being said, OneGet installs my hydrus package just fine, and what with v188 already stuck in moderation for several days, having the ability to check for updates doesn't count for much if updates are going to be hidden from view. You can manually specify the desired version of the package you want to bypass moderation through OneGet, too. 188 isn't "approved" by chocolatey yet, so any of the following is fine.

OneGet:

Install-Package hydrus-network -RequiredVersion 188.0

Chocolatey:

choco install hydrus-network –version 188.0

cinst hydrus-network –version 188.0

Anonymous 01/02/16 (Sat) 12:59:50 No.1688

>1687

Some corrections

-OneGet's chocolatey "provider" (client, implementation, whatever) is 2 years out of date, which accounts for all the problems I listed.

-Chocolatey is currently (at least partially) written in C#, I don't know why they haven't given OneGet an official thing to include yet.

https://github.com/chocolatey/choco/wiki/ChocolateyFAQs#how-is-chocolatey-different-than-onegetpowershell-package-management

Anonymous 01/14/16 (Thu) 05:16:03 No.1774

>>1663

>unless I get "trusted status" (not likely anytime soon)

I'll be damned, they trusted the hydrus package already (or intended to, I see a moderation comment saying they trusted it, but usually there's a banner showing trusted status).

All updates should be available to you guys as soon as I push them.