WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: dry-run for importsce  (Read 3286 times)

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
dry-run for importsce
« on: November 01, 2013, 12:24:50 PM »
hi roberts,

in the moment it's a bit difficult to estimate the size a package with all the included dependencies.
is it possible to do a dry-run of importsce to calculate the size of the package and to show the dependencies, perhaps even the additional dependencies that need to be downloaded.

thank you for your work and commitment.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: dry-run for importsce
« Reply #1 on: November 01, 2013, 01:29:49 PM »
In native core we have ready made .tree files for such purposes.
With the vast catalog of Debian, no such .tree files exist.

Will have to reflect with team on this as the user effort may not be worth the result.
10+ Years Contributing to Linux Open Source Projects.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
Re: dry-run for importsce
« Reply #2 on: November 01, 2013, 11:42:36 PM »
hi roberts,

thank you for reflecting upon this topic.
a "quick and dirty"-approach could be a modified importsce-command without downloading new packages,
but reporting missing packages with their sizes and without mksquashing the sce-package at the end ;)
« Last Edit: November 01, 2013, 11:49:04 PM by netnomad »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: dry-run for importsce
« Reply #3 on: November 06, 2013, 03:30:11 PM »
Hi netnomad,

This was looked into and the deciding factor against it is that it would require the re-introducing of a couple of fields in the Packages file that would slow down performance for everyone.  In other words it could be done, but decided it is not worth the performance cost.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
Re: dry-run for importsce
« Reply #4 on: November 06, 2013, 09:28:18 PM »
hi jason w,

thank you that you considered the different options.