From: Michael Shigorin <mike@osdn.org.ua> To: community-en@altlinux.org Subject: Re: [Comm-en] Sisyphus.....Alt.....few questions Date: Fri, 11 Jul 2003 16:51:24 +0300 Message-ID: <20030711135124.GH873@osdn.org.ua> (raw) In-Reply-To: <3F0EAEE0.5090100@amnet.co.cr> On Fri, Jul 11, 2003 at 06:34:40AM -0600, Chad wrote: > I would like to try some of the Sisyphus packages. I do NOT > want to mess up my current install of AltJr2.2. Wise. > Is it best to do a second intall of AltJr2.2 Yes; I also do that when testing some new release to upgrade to (or another distro). > do all the updates and they go to the repositories and select > the sisyphus repositories? Ugh. Explain yourself :-) updates/ are *stable* updates, Sisyphus/ is an unstable (developers') branch. Rare packages tested in Sisyphus would be backported/repackaged as updates if they fix security or critical bugs. > Then update everything sisyphus or can I just do certain > progams? Basically, you can do with several programs, but till some base component (like libqt3) changes enough to drag all its dependencies after itslef. The recommended way is dist-upgrade (total), still sometimes binary "refresh" goes OK, and in most situations it's possible to rebuild src.rpm from Sisyphus on a previous stable install with development. I've been practicing that at home but now am mostly using Sisyphus at work and Master+updates at home and on servers, though home system sometimes gets newer things like kernel/alsa which I want to test on yet another hardware sample. All in all, using Sisyphus is recommended with broadband at hand, and the packages downloaded could be backed up from /var/cache/apt/packages just in case you want to bring them somewhere else or redo something from scratch. -- ---- WBR, Michael Shigorin <mike@altlinux.ru> ------ Linux.Kiev http://www.linux.kiev.ua/
prev parent reply other threads:[~2003-07-11 13:51 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-11 12:34 Chad 2003-07-11 13:51 ` Michael Shigorin [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030711135124.GH873@osdn.org.ua \ --to=mike@osdn.org.ua \ --cc=community-en@altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux users (in English only) This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community-en/0 community-en/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community-en community-en/ http://lore.altlinux.org/community-en \ community-en@lists.altlinux.org community-en@lists.altlinux.ru community-en@lists.altlinux.com public-inbox-index community-en Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community-en AGPL code for this site: git clone https://public-inbox.org/public-inbox.git