Bug 171361 - ports-mgmt/pkg: Regressions from pkg_ tools
Summary: ports-mgmt/pkg: Regressions from pkg_ tools
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Baptiste Daroussin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-06 02:50 UTC by Benjamin Close
Modified: 2018-02-20 13:28 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Close freebsd_committer freebsd_triage 2012-09-06 02:50:02 UTC
I'm in the process of testing pkgng:

benjsc@taurus:/usr/ports | pkg -v
1.0

Overall I've very impressed. However I've discovered a number of features that appear to be a regression from what is currently available via the pkg_ tools. I've listed these below.

1> Package fetch continue

I have a intermittent network connection. If a package fails part way through download, the entire package is refetched. When your connection drops out 5 times downloading qt-docs (100mb) this is a big issue. Please implement fetch continue (as fetch does)

2> Unable to multiple instances of pkgng at the same time.

If I have one instance of pkg installing then at the same time you can't perform commands which would be read only. Ie status, which, etc. 

This is a regression from the old pkg_info where you could query at the same time

3> Not a regression but a bug:  

pkg check -a

doesn't work.

4> No documentation on meaning of kb/ status when fetching

When fetching 2 stats displaying kb's are displayed. There is no documentation on the meaning of these. The first appears to be kb/s the second I could not find a meaning for:


qt4-doc-4.8.2.txz                                       100%   95MB  66.7KB/s  94.5KB/s   24:20    
                                                                                                         ^^^^^^^^
                                                                                                         What's this?

5> auto remove after pkg2ng finds no candidates

After using pkg2ng there is no candidates listed. I'm sure some packages could be auto removed

6> pkg checks for updated reposity information every time install is run

If I chose a package to install then upon running install an update run is also performed. Update should be it's own task and not related to install. (I might want the current version not a later version)

7> pkg2ng needs to provide some help.

Upon a completed run of pkg2ng I ran pkg update. 
Only to be told no repository is found. An easy fix but I had to work out what it was. Perhaps a one line printf indicating that a config file is needed and an example in /usr/local/etc/pkg.conf.sample is available. It'd just make it much more user friendly for anyone trying pkg2ng out.

Thanks and keep up the good work.

Ben

How-To-Repeat: 1> 

pkg install qt4-docs
<pull network cable out>
pkg install qt4-docs

2> 

pkg install qt4-docs

Whilst download is running

pkg which /usr/local/bin/bash

Result:

benjsc@taurus:/usr/ports | pkg which /usr/local/bin/bash
pkg: sqlite: database is locked (pkgdb.c:2363)

5> 

pkg2ng
pkg autoremove

6> 

root@taurus:/home/benjsc $BUILD_ENV$GITBRANCH| pkg install virtualbox-ose virtualbox-ose-kmod
Updating repository catalogue
Repository catalogue is up-to-date, no need to fetch fresh copy
The following packages will be installed:


Same for status, version etc.

3>
 
benjsc@taurus:/usr/ports | pkg check -a
usage: pkg check [-Bdsr] [-vy] [-a | -gxX <pattern>]

For more information see 'pkg help check'.
Comment 1 Jason Helfman freebsd_committer freebsd_triage 2012-09-06 05:55:47 UTC
Responsible Changed
From-To: freebsd-ports-bugs->bapt

fix sysopsis, and assign
Comment 2 Baptiste Daroussin freebsd_committer freebsd_triage 2012-09-06 08:07:52 UTC
Thank you very much for highly constructive feedback, we have taken
the PR and put it into our github system
(https://github.com/pkgng/pkgng/issues/348).

We will try to fix as much as possible of the issues your raised.

Concerning pkg2ng, I'm sorry but there is no way for it to be able to
figure out what you decided to intall on purpose of not.

What could be done (and will be :)) is to propose a tool to let should
chose what you really want to keep and mark the rest as automatic.

A user has already contributed a dialog based tool for this, I haven't
taken time to review yet but I want it in pkgng 1.1

This PR will be close only when all the issues will have been adressed
along with a new release of pkg

regards,
Bapt
Comment 3 Bryan Drewery 2012-09-06 15:38:05 UTC
(3) pkg check -a

Please see pkg-check(8). You must specify -B, -d, -r or -s to tell
pkg-check what to actually check for.

Bryan
Comment 4 Carlo Strub freebsd_committer freebsd_triage 2014-09-11 20:01:19 UTC
Is this PR still relevant?
Comment 5 Walter Schwarzenfeld freebsd_triage 2018-01-08 15:35:52 UTC
I don' think this still relevant.