Re: rpm question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Dec 17, 2008, at 7:31 AM, Tim Born wrote:

You can create an RPM that just lists other RPMs as dependencies.
When you install the first, all the rest will follow.
Works slick.  The spec file is trivial.


Sure an empty package that carries Requires: to other
packages works slick. This is (more or less) the analogue
of a Debian task package. It has also been used by
DSV's (distro software vendors) to hide system
dependencies underneath a package that contains
only a single
	Provides: LSB
as dictated by LSB packing policies in order to satisfy
LSB conformance.

But there are still some minor flaws with a
task package approach. First of all, a task
package is mostly useless after its been installed,
there is no content within the package. There
is already an RFE for "melting" packages,
i.e. packages that are not registered, are solely
used to carry dependency information) at
	https://bugzilla.redhat.com/show_bug.cgi?id=474704
And there is also a proposed solution that is irrelevant on <rpm-list@xxxxxxx >, per-moderator.

But there's a deeper flaw using "task packages" instead of "package bundles",
an immense amount of depsolver overhead is also needed, and there is
the additional need for more Requires: dependencies in the task package,
bloating repository metadata representations, and otherwise leading
to an increased number of packages.

A "package bundle" done correctly has this major advantage over a "task package":
	Its simple. everything needed is contained within the "package bundle"

If done correctly (my private ideas, irrelevant to <rpm-list@xxxxxxx> per moderator), then there is also a reduction in the number of dependencies that need to be carried around in repository metadata. All Requires: dependencies that are satisfied within
a "package bundle" need not be exposed in the "package bundle" wrapper.

hth

73 de Jeff

best,
-tm

John Frazier wrote:
I would like to build an rpm that does nothing but install other rpms.
My idea is that I can use this rpm to manage and track groups of rpms
that have been installed on our systems. Is this just crazy or is it
feasible. I look forward to hearing from you any alternate ideas would
be greatly appreciated as well.

Best Regards,

John Frazier
------------------------------------------------------------------------
Send e-mail faster without improving your typing skills. Get your
Hotmail® account.
<http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008 >

------------------------------------------------------------------------

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list



--
"The master in the art of living makes little distinction between his
work and his play, his labor and his leisure, his mind and his body,
his education and his recreation, his love and his religion. He simply
pursues his vision of excellence in everything he does, leaving others
to determine whether he is at work or at play.  To him, he is always
doing both."

- Zen

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux