Mailinglist Archive: opensuse-factory (420 mails)
| < Previous | Next > |
Re: [opensuse-factory] suggested work around for zypper/libzypp
- From: James Tremblay <jamesat@xxxxxxxxxxx>
- Date: Thu, 04 Oct 2007 10:44:12 -0400
- Message-id: <1191509054.3620.21.camel@xxxxxxxxxxxxxxxxxxxxx>
On Thu, 2007-10-04 at 16:36 +0200, Stanislav Visnovsky wrote:
> Dňa Thursday 04 October 2007 16:24:43 Carlos E. R. ste napísal:
> > The Thursday 2007-10-04 at 10:00 -0300, Gabriel . wrote:
> > >> I agree that on a running system, this is not the most effective
> > >> approach. What needs to be determined is to figure out how much space
> > >> you can spare to download the packages and this is not very easy to do.
> > >> Just imagine a package that will need to create a big new file in its
> > >> post-install script (think initrd for a new kernel). You can hardly
> > >> predict, only to use heuristics.
> > >
> > > I agree, but it could be an option (where the user configures the
> > > repos) to choose what method will be used.
> >
> > Remember that till suse 10.0 that was what was done. Yast first downloaded
> > all, then installed all, then removed or kept (user option) all files.
> >
> > The point is to reinstate the old behaviour.
>
> Are you sure about this?
>
> Stano
I would prefer it , if only as a choice. Netware has always done it this
way to preserve the ability to back rev a file or the whole system in
case of failure or conflict between the "update" and another piece of
software installed.
--
James Tremblay
Director of Technology
Newmarket School District
213 S. Main st
Newmarket NH, 03857
603-659-3271 *318
CNE 3,4,5
MCSE w2k
CLE in training
Registered Linux user #440182
http://en.opensuse.org/educationk
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
> Dňa Thursday 04 October 2007 16:24:43 Carlos E. R. ste napísal:
> > The Thursday 2007-10-04 at 10:00 -0300, Gabriel . wrote:
> > >> I agree that on a running system, this is not the most effective
> > >> approach. What needs to be determined is to figure out how much space
> > >> you can spare to download the packages and this is not very easy to do.
> > >> Just imagine a package that will need to create a big new file in its
> > >> post-install script (think initrd for a new kernel). You can hardly
> > >> predict, only to use heuristics.
> > >
> > > I agree, but it could be an option (where the user configures the
> > > repos) to choose what method will be used.
> >
> > Remember that till suse 10.0 that was what was done. Yast first downloaded
> > all, then installed all, then removed or kept (user option) all files.
> >
> > The point is to reinstate the old behaviour.
>
> Are you sure about this?
>
> Stano
I would prefer it , if only as a choice. Netware has always done it this
way to preserve the ability to back rev a file or the whole system in
case of failure or conflict between the "update" and another piece of
software installed.
--
James Tremblay
Director of Technology
Newmarket School District
213 S. Main st
Newmarket NH, 03857
603-659-3271 *318
CNE 3,4,5
MCSE w2k
CLE in training
Registered Linux user #440182
http://en.opensuse.org/educationk
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |