The openslp ebuild in portage is quite old, so I decided to tyke a shot at updating both stable (1.2.0) and development (1.3.0) versions. I realize ZeroConf is getting all the attention these days (provided e.g. by Howl) but maybe someone has use for continued SLP support (cups?). Reproducible: Always Steps to Reproduce: The build process seems to have changed somewhat; running autogen.sh followed by configure in the source directory results in broken Makefiles (good old 'not a separator' and lots of @AM_..@ leftovers). I added autoreconf and that seems to fix everything, i.e. the generated Makefiles actually work. I have no idea whether this is the 'right thing' to do, but it does result in a building source tree, so it can't be all wrong..
Created attachment 48030 [details] new ebuild for openslp-1.2.0 ('stable')
Created attachment 48031 [details] new ebuild for openslp-1.3.0 ('development')
Things to fix: * Set KEYWORDS as per policy * No need for that DEPEND * No emake? * Can't use make DESTDIR=${D}? * What's ${FILESDIR}/slpd-init?
Created attachment 48379 [details] new ebuild for openslp-1.2.0 ('stable') fixed KEYWORDS, use emake
Created attachment 48380 [details] new ebuild for openslp-1.3.0 ('development') fixed KEYWORDS, use emake
I fixed KEYWORDS (not sure if I understood that right: new ebuilds are suppoosed to start only on the ~arch that I have?), removed that DEPEND and now use emake; both still build fine. I'm afraid I don't know what to do about DESTDIR. Like I said, the whole autoconf/automake process changed from the older ebuild and looks somewhat derailed. slpd-init is the init script installed for the slpd daemon, just as in the old ebuild already in portage.
sorry, don't think i can take on any new ebuilds like this. maybe the printers people might know more because some printers use SLP?
1.2.1 is now in stable. i'll defer on 1.3.0 until it comes out of development.
