[PlanetCCRMA] Re: (newbie) questions on the FC5 CCRMA and package management

Axel Thimm planetccrma@ccrma.Stanford.EDU
Thu Jul 20 13:48:02 2006


--mvpLiMfbWzRoNl4x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 20, 2006 at 07:40:44PM +0200, Nigel Henry wrote:
> On Thursday 20 July 2006 03:31, Axel Thimm wrote:
> > On Wed, Jul 19, 2006 at 08:57:24PM +0200, Nigel Henry wrote:
> > But personal preferences aside: Note that any half-enabled repo is
> > doomed to break. Don't recommend to people to selectively/partially
> > enable repos on demand as some dependencies will break. It is better
> > to never use a repo than to create bugs by wrong usage.
>=20
> My suggestion, was only related to apps like unrar, lame, etc, that are n=
ot=20
> available from Fedora, and do not have any specific dependencies.

So you need to add "for trivial packages only", but it is seldom that
a package isn't aprt of a larger dependency group.

> Of course I need to keep some sort of record as to where I got these extr=
a=20
> packages from,

And you (or the user taking the advice from you) need to analyze the
depednecies and check whether you need to pull more packages and
records that for the future, too. And that is so involved that noone
will do. Instead people will only tkae half the advice. half-enable
the repo and we repo maintainers have to fight the resulting bugs.

> As I've stated above, I was referring to specific packages that are not=
=20
> available from the Fedora repos. I have no experience of using another re=
po,=20
> yours for instance, for all system, and anything else upgrades, apart fro=
m=20
> planetccrma. I certainly would not recommend getting upgrades to your sys=
tem=20
> from more than one repo, as, as you have stated, you could end up with a=
=20
> broken setup.

Ooops, I never said that! On the contrary I promote concurrent (full)
usage of different repositories.
--=20
Axel.Thimm at ATrpms.net

--mvpLiMfbWzRoNl4x
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQFEv+voQBVS1GOamfERAr7aAJ9S4d6U6NDsFhsD7UMASm+GO5kP+ACbBvvg
LgREHUe92gDMUHvWOaCUeYg=
=0fvf
-----END PGP SIGNATURE-----

--mvpLiMfbWzRoNl4x--