<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#cccccc" text="#000000">
Hey Guys,<br>
I should have clarified. I only use slapt-get when gslapt doesn't do
what I need it to. I suggested this only for the benefit of gslapt, not
slapt-get. And since gslapt cannot work without slapt-get, I suggested
this to be added to the slapt-getrc file, since it is used by gslapt
also. Most of the time (99.9%), I never even use slapt-get directly. I
do however keep gslapt open at all times. Once open, it is never
closed. I use gslapt as my package browser. I could use Webmin for
this. But gslapt is more direct. I only (rarely) use pkgtool to see the
individual files in each package. That's why I've asked for many other
features to be added to slapt-get also. Not so much because slapt-get
can't do the things I've asked for, but because gslapt can't do
anything that slapt-get won't do.<br>
<br>
I only want to use gslapt. I want to include those packages I currently
have as EXCLUDE(d), with those which are regularly upgraded. That's
what prompted this. I hope this now explains why none of the command
line comments made in response to this have any application to my
intent. Now, if after this lengthy explanation, there is still no
desire to acknowledge the basis of difference, however slight it may
seem to some of you, I don't see any point in discussing this any
further.<br>
<br>
I only suggested this as a means to increase the functionality of
gslapt. Gslapt has an entirely different set of functions by being
graphical that slapt-get provides. I like to see what I'm working on,
and be able to make immediate comparisons. What can be done with
slapt-get on the command line is irrelevant. So, if this feature won't
be added, please don't ask me any more questions about it. I don't
think there's anything more to be added to this explanation. And I
won't bother.<br>
<br>
Shingoshi<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:woodwardj@jaos.org">woodwardj@jaos.org</a> wrote:
<blockquote id="mid_200901240129_n0O1TK4l031462_jaos_org"
cite="mid:200901240129.n0O1TK4l031462@jaos.org" type="cite">
<pre wrap="">
</pre>
<blockquote id="StationeryCiteGenerated_6" type="cite">
<blockquote id="StationeryCiteGenerated_7" type="cite">
<pre wrap="">EXCLUDE won't DOWNLOAD_ONLY. EXCLUDE forbids everything listed on that
line from being installed. If there were a DOWNLOAD_ONLY option,
packages listed there could be handled (downloaded) with all of the
other packages that would normally be installed. EXCEPT those
DOWNLOAD_ONLY packages would only be downloaded, not installed.
That means if there is a kernel upgrade available, all of the kernel
packages would automatically be downloaded, leaving them for the user to
install them manually. That's the difference. The same would be true for
glibc, alsa* and many of the others that are needed by the system
(currently listed as EXCLUDE), but require special user attention before
and or after installation.
The EXCLUDE option should be left for packages that you NEVER want
installed under any circumstances.
</pre>
</blockquote>
<pre wrap="">That's incorrect. EXCLUDE can be overridden with the --install option,
when you're ready to deal with the package upgrade. I use this with php,
so I can EXCLUDE it from general upgrades, and explicitly install it
when I'm ready to compile related dependencies. I also use it for things
like glibc-zoneinfo, which is EXCLUDEd by default.
</pre>
</blockquote>
<pre wrap=""><!---->
Jorey is right. --install obeys the request.
If you check the documentation, for example the man page for slapt-get(8), then you should be
able to see how you'd accomplish what you are after:
--download-only|-d
Download the package only. Do not install/upgrade. Packages
are downloaded to /var/slapt-get/.
--ignore-excludes
Ignore exclude list and install excluded packages anyway.
So if you do the following:
slapt-get --upgrade --ignore-excludes --download-only
Then it will download all upgrades regardless of their exclude status. Please also take a look
at the --no-upgrade option that is there specifically for the kernel use case:
--no-upgrade
Install the package rather than attempting to detect if a pre&#8208;
vious version is installed and upgrading it. This is useful
for installing kernel packages. This option is only valid for
--install targets.
take care,
jason
--
Jason Woodward
<a class="moz-txt-link-abbreviated" href="mailto:woodwardj@jaos.org">woodwardj@jaos.org</a>
_______________________________________________
Slapt-get-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Slapt-get-user@software.jaos.org">Slapt-get-user@software.jaos.org</a>
<a class="moz-txt-link-freetext" href="http://software.jaos.org/cgi-bin/mailman/listinfo/slapt-get-user">http://software.jaos.org/cgi-bin/mailman/listinfo/slapt-get-user</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<img src="cid:part1.05050208.03000803@comcast.net" border="0"></div>
</body>
</html>