Message: previous - next
Month: November 2011

Re: [trinity-devel] KOffice Suite

From: Kristopher John Gamrat <chaotickjg@...>
Date: Tue, 22 Nov 2011 16:50:20 -0500
On Tuesday 22 November 2011 04:48:42 pm Robert Xu wrote:
> On Nov 22, 2011, at 16:28, Kristopher John Gamrat <chaotickjg@...> wrote:
> >
> >
> > On Tuesday 22 November 2011 04:23:35 pm Darrell Anderson wrote:
> >>>> Well, then. Looks like I need to learn how to package
> >>> the apps separately. Can anybody here help with that? A mini
> >>> how-to?
> >>>
> >>> You'd need to separate the files into different packages.
> >>> Put the core libraries in one package, then separate the
> >>> binaries and other libraries into other packages. If you use
> >>> RPM for package management, I can provide an example of how
> >>> to do that. I don't know how to do packaging on any other
> >>> system.
> >>
> >> I don't use RPM, but I can uncompress rpms. As long as the build scripts are inside the rpm I probably can convert the build scripts to Slackware.
> >
> > SRPMs (source RPMs) contain the build scripts, and can be installed/unpacked the same as binary RPMs. From talking with others, though, I'm not sure how many distros actually use SRPMs. Some put their spec files (the build script) and sources in either tarballs or version control.
> All >_> a SRPM gives an RPM ^_^

Spec files and source code give the RPM, and are included in the SRPM. Any system that uses SRPMs to build the RPMs always unpack the SRPM first to get at the spec files and source code. Not all RPM-based build systems use (or accept) SRPMs, some do.
> And most distributions use subpackages for this kind of stuff, so
> converting build scripts can be tricky.
> Either that or highly annoying >.<

That's something the package maintainers have to decide -- to convert, or write from scratch.

Kristopher Gamrat
Ark Linux webmaster