vpkg-project / vpkg Goto Github PK

View Code? Open in Web Editor NEW

115.0 4.0 10.0 247 KB

An alternative package manager for V.

Home Page: https://vpkg-project.github.io

License: MIT License

V 100.00%

vlang v package-manager vpm registry-vpkg vpkg registry-server vpkg-registry

vpkg's People

Contributors

Stargazers

Watchers

Forkers

eregnier isgasho dhonx moneytech djoodle nearvarna refaqtor watzon mrmidnightofficial smartiniongithub

vpkg's Issues

Compile error

PS E:\code\v> v build .\vpkg
vpkg\api\lockfile.v:36:5: error: unexpected lock, expecting name
34 |
35 | fn get_lockfile_path(dir string) string {
36 | return os.join_path(dir, '.vpkg-lock.json')
| ~~~~
37 | }
38 |

Missing license

I just realized that neither vpkg or the registry have an open source license in their repository. Would it be possible to add one?

Error in decode() for api__Lockfile error_ptr=: %s

Error in decode() for api__Lockfile error_ptr=: %s
0 package was installed successfully.

Where is the cause?

Error when running vpkg-0.7.1 for Linux

Hi,
running latest package (prebuilt) of vpkg (vpkg-0.7.1-linux) in a Ubuntu 19.10 PC x64 I get the following error:

vpkg-0.7.1-linux: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

But if I checkout sources and build with latest V stable (0.1.24), and run the built version all is good.
I wonder if the same happens to someone other, or if binary package as to be rebuilt.
Dimensions of files are different:

-rwxr-xr-x 1 sandrom users 283480 feb 14 16:45 ./vpkg-0.7.1-linux*  -> downloaded binary
-rwxr-xr-x 1 sandrom users 185744 mar 19 17:58 /usr/local/bin/vpkg*  -> built today

Last, note that if I try to build with latest V sources I got compilation errors but I know there are too many moving parts in V at the moment.

Hope it's good to someone other.
Bye, sandro

windows 10/ cmake 3.18.0-rc2 fails building devil

vcpkg install devil:x86-windows-static
Computing installation plan...
The following packages will be built and installed:
devil[core,jasper,lcms,libjpeg,libpng,openexr,tiff]:x86-windows-static

libffi[core]:x86-windows-static
liblzma[core]:x86-windows-static
libpng[core]:x86-windows-static
openexr[core]:x86-windows-static
openssl[core]:x86-windows-static
openssl-windows[core]:x86-windows-static
python3[core]:x86-windows-static
tiff[core]:x86-windows-static
zlib[core]:x86-windows-static
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x86-windows-static...
Starting package 1/10: zlib:x86-windows-static
Building package zlib[core]:x86-windows-static...
Could not locate cached archive: C:\Users\Ira\AppData\Local\vcpkg\archives\d3\d3bcac927dea0086928c96d44671fdb8b635db43.zip
-- Using community triplet x86-windows-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\Program Files (x86)\vcpkg\triplets\community\x86-windows-static.cmake
-- Using cached C:/Program Files (x86)/vcpkg/downloads/zlib1211.tar.gz
-- Cleaning sources at C:/Program Files (x86)/vcpkg/buildtrees/zlib/src/1.2.11-deec42f53b.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Program Files (x86)/vcpkg/downloads/zlib1211.tar.gz
-- Applying patch cmake_dont_build_more_than_needed.patch
-- Using source at C:/Program Files (x86)/vcpkg/buildtrees/zlib/src/1.2.11-deec42f53b.clean
-- Configuring x86-windows-static
-- Building x86-windows-static-dbg
-- Building x86-windows-static-rel
-- Fixing pkgconfig
-- Acquiring MSYS2...
-- Using cached C:/Program Files (x86)/vcpkg/downloads/msys2-base-x86_64-20190524.tar.xz
-- Using cached C:/Program Files (x86)/vcpkg/downloads/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
-- Using cached C:/Program Files (x86)/vcpkg/downloads/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
gpg: Generating pacman keyring master key...
gpg: key A6D47F70EE8A91DE marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/39E602025AD01355238440F1A6D47F70EE8A91DE.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from msys2.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
-> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
-> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
-> Locally signing key 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 4 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 4 signed: 3 trust: 0-, 0q, 0n, 4m, 0f, 0u
gpg: depth: 2 valid: 3 signed: 0 trust: 3-, 0q, 0n, 0m, 0f, 0u
/usr/bin/bash: -c: line 0: syntax error near unexpected token (' /usr/bin/bash: -c: line 0: PATH=/usr/bin;pacman-key --verify C:/Program Files (x86)/vcpkg/downloads/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig'
CMake Error at scripts/cmake/vcpkg_acquire_msys.cmake:114 (message):
Cannot verify MSYS2 keyring.
Call Stack (most recent call first):
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:281 (vcpkg_acquire_msys)
ports/zlib/portfile.cmake:46 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:79 (include)

`release` command updates version incorrectly

I have a package with v.mod contains version set to 0.2.0.

When I run vpkg release --inc patch it sets version to v0.2.00.2.1.
When I run vpkg release --inc minor it sets version to v0.2.00.1.0.
When I run vpkg release --inc major it sets version to v0.2.01.0.0.

I tried to change version in v.mod to other ones (e.g. 1.0.0, 0.0.1, the result is similar).

There's a keyword `lock` that was introduced, I think.

Any news on updates?

Versioning

How is versioning handled? If I understood the code right, the "update" command always updates to the most current commit in a repository.

If that's the case, wouldn't it make more sense to get the repository at the commit in which the version number has been changed or something like that? A new version would then be created when the version number in vpkg.json changes.

vpkg get and vpkg update fail if the lock file is missing (and it is right after vpkg init)

0[11:37:12]delian@nemesis: /v/vpkg/xxx $ vpkg init
Package manifest file was created successfully.
0[11:37:15]delian@nemesis: /v/vpkg/xxx $ ls -la
total 12
drwxrwxr-x 2 delian delian 4096 сеп 22 11:37 ./
drwxrwxr-x 4 delian delian 4096 сеп 22 11:37 ../
-rw-rw-r-- 1 delian delian  161 сеп 22 11:37 vpkg.json
0[11:37:16]delian@nemesis: /v/vpkg/xxx $ cat vpkg.json
{
   "name": "xxx",
   "version": "1.0"
   "author": ["Author Name <[email protected]>"],
   "repo": "https://github.com/username/repo",
   "dependencies": []
}0[11:37:18]delian@nemesis: /v/vpkg/xxx $ vpkg get
Cannot read /v/vpkg/xxx
Error in decode() for Lockfile error_ptr=: %s
0[11:37:32]delian@nemesis: /v/vpkg/xxx $ ls -la
total 16
drwxrwxr-x 2 delian delian 4096 сеп 22 11:37 ./
drwxrwxr-x 4 delian delian 4096 сеп 22 11:37 ../
-rw-rw-r-- 1 delian delian  161 сеп 22 11:37 vpkg.json
-rw-rw-r-- 1 delian delian   42 сеп 22 11:37 .vpkg-lock.json
0[11:37:45]delian@nemesis: /v/vpkg/xxx $ cat .vpkg-lock.json
{
   "version": "0.5",
   "packages": []
}0[11:37:48]delian@nemesis: /v/vpkg/xxx $ vpkg get
0 package was installed successfully.
0[11:37:50]delian@nemesis: /v/vpkg/xxx $ vpkg update
Fetching lockfile
Updating packages
0 package was updated successfully.
0[11:38:07]delian@nemesis: /v/vpkg/xxx $ ls -la
total 16
drwxrwxr-x 2 delian delian 4096 сеп 22 11:37 ./
drwxrwxr-x 4 delian delian 4096 сеп 22 11:37 ../
-rw-rw-r-- 1 delian delian  161 сеп 22 11:37 vpkg.json
-rw-rw-r-- 1 delian delian   46 сеп 22 11:38 .vpkg-lock.json
0[11:38:10]delian@nemesis: /v/vpkg/xxx $ rm .vpkg-lock.json
0[11:38:16]delian@nemesis: /v/vpkg/xxx $ vpkg update
Fetching lockfile
Cannot read /v/vpkg/xxx
Error in decode() for Lockfile error_ptr=: %s
0[11:38:19]delian@nemesis: /v/vpkg/xxx $ vpkg update
Fetching lockfile
Updating packages
0 package was updated successfully.
0[11:38:20]delian@nemesis: /v/vpkg/xxx $

Bug when running `vpkg install`

When running vpkg install command. vpkg will add a new item in the dependencies field on vpkg.json file.

and also the unhandled information

Is "vpkg" still active?

This is just a question. As I don't see any more commits since April 18.

[BUG] v.mod gets overwritten

When running a vpkg command many lines in the v.mod file are deleted.

Module {
	name: 'symlinker',
	description: 'Utility to manage symlinks',
	author: 'Lukas Neubert <[email protected]>',
	license: 'MIT',
	repo_url: 'https://github.com/Serkonda/symlinker',
	version: '0.4.0',
	dependencies: ['chalk']
}

is stripped down to this:

Module {
    name: 'symlinker',
    version: '0.4.0',
    deps: ['chalk']
}

First error is that the deps property is not conform with the official v.mod and should be changed to dependencies.

Second I think that vpkg should not alter any line except the dependencies array. So that all the other information is kept.