Package breakup

[Brendon Costa <brendon%christian.net@localhost>]

Hi all,

I am looking at creating a new pkgsrc package for a project I am working
on (First time creating a pkgsrc package). I will be creating packages
for the next release when it is out:

http://edoc.sourceforge.net/

I am also looking at creating redhat, and debian packages for it. I have
noticed that often redhat and debian packages are broken into different
"sub-packages" like:

edoc
libedoc
libedoc-dev

(Could even break down more into additional libraries that interoperate
with libedoc)
libedocpy
libedocpy-dev
libedocbfd
libedocbfd-dev

but really this breaking down of packages seems like it can be a lot of
work!


Is this a bad idea for pkgsrc, i.e. should i just create a single "edoc"
package that installs everything for pkgsrc?

Also for the other package types i have special rules in my build system:

make deb
make rpm

that will build binary packages using those systems and place the
rpm/deb package files in the root build directory. As i understand it
pkgsrc packages need to be built in the pkgsrc tree. Is this definitely
the case or is there some method of integrating the building of binary
pkgsrc packages into my projects automake files?

Thanks,
Brendon.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss