[SOLVED] Rethinking the description during install?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You mean like: don't add a test for an environment variable to be used to apply this option or not?
That should be fine.
My experiments with modifying the installer were confined to adding support for ntfs-3g as I wanted to PXE boot a minimal system on some Windows machines for imaging to an NTFS formattted external USB drive. I did come across some differences in the BusyBox versions of commands while playing with this. This was the source of my comment.
I'd rather see a list of packages being installed scroll by, one package name per line (with size info). Even that might get hard to read during the buzz of small packages being installed causing rapid scrolls.
It's not that bad. Really doesn't matter much to me what scrolls by. Most of the time I don't sit and watch.
You could always opt for prompt for everything, then there would be no problem reading.
Last edited by chrisretusn; 03-18-2011 at 09:17 PM.
Sat Mar 19 04:37:14 UTC 2011
a/pkgtools-13.37-noarch-2.tgz: Rebuilt.
Add --terse one-line output mode to installpkg.
I thought I would just try this out on one of my own self made packages:
Code:
# installpkg --terse opera-11.10.2053-i386-1ro.txz
opera-11.10.2053-i386-1ro: fast and secure web browser and Internet suit [30M]
# grep -A1 DESCRIPTION /var/log/packages/opera-11.10.2053-i386-1ro
PACKAGE DESCRIPTION:
opera: A fast and secure web browser and Internet suite.
What happened to 'A' from the start and 'e.' from the end in the terse output? It seems like it is cropping from either end.
Probably not a major issue if you realise what it is doing but it might cause some people to be confused depending on how the description has been written.
I thought I would just try this out on one of my own self made packages:
Code:
# installpkg --terse opera-11.10.2053-i386-1ro.txz
opera-11.10.2053-i386-1ro: fast and secure web browser and Internet suit [30M]
# grep -A1 DESCRIPTION /var/log/packages/opera-11.10.2053-i386-1ro
PACKAGE DESCRIPTION:
opera: A fast and secure web browser and Internet suite.
What happened to 'A' from the start and 'e.' from the end in the terse output? It seems like it is cropping from either end.
Probably not a major issue if you realise what it is doing but it might cause some people to be confused depending on how the description has been written.
Your slack-desc file does not conform to the specs.
The first line should look like:
Code:
pkgname: pkgname (short description)
Since the first line of your slack-desc file is lacking the ( ) the effect of "--terse" is that the first and last character of your short description are cut off instead of the "(" and ")".
I think I originally read about the formatting of the slack-desc here http://slackwiki.org/Slack-desc and looking back now it isn't clear on this point. Though I see from looking at the official packages that the method you describe is clearly correct.
I think I originally read about the formatting of the slack-desc here http://slackwiki.org/Slack-desc and looking back now it isn't clear on this point. Though I see from looking at the official packages that the method you describe is clearly correct.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.