[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why not create packages?
Dan York wrote:
> Gary & David wrote:
> > >>>>> "D" == David Merrill <email@example.com> writes:
> > D> Dan York is stepping up to the plate and offering to do the
> > D> work; why not let him?
> > If Dan has the resources to handle all the 140+ Linux distributions,
> > and he wants to host the resulting archive, then I say go for it, but
> > my expert opinion is that this is madness.
> Ummm... I am willing to *help* with creating packages, but I don't
> have the time, resources, or expertise to do it all myself.
Should have written, "offering to do^H^Hhelp with the work".
> I guess I didn't realize that the differences were so severe between
> the various RPM-related distros and between Debian and Corel. I
> thought that RPMs were basically the same, although admittedly they
> put them in potentially different directories.
If they are different, they ought *not* to be. There's no vendor
specific requirement for this, and if it's not in the FHS it should be.
> Perhaps LDP should specify a distribution-neutral location for all
> the HOWTOs, such as /opt/doc or /opt/ldp. Or perhaps this is /usr/doc.
> It just seems like there should be a place for them to always reside.
> Then the packages could just install into that dir and they could
> work across all distros.
Does anyone know the FHS guideline? I just looked on their website at
the 2.0 version, but didn't even see /usr/doc listed. Seemed strange;
maybe it was temporary blindness or something.
> And perhaps it's just too much of a pain in the neck.
Maybe so. But I'd also be willing to help. It can't be that hard to
auto-generate current rpms in a script. I don't know anything about
debian, but I've used rpm a little.
David C. Merrill, Ph.D.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com