synce ebuilds

[Iain Buchanan]

Hi Lucian,

I don't think I've responded to you about this - sorry! I just changed
mail clients twice recently, so your email got unmarked.

Hello Iain,
I managed to write some new ebuilds for synce and am sending you the
diffs to the current ones. They might need some more tweaking, but maybe
they help.

Thanks, but unfortunately my sandbox is in a state of flux at the
moment, so a diff would be quite difficult for me to use. Are you able
to tar up the actual ebuild files that you've changed, and I can diff
them when I have a more-stable set of ebuilds?

If you find them useful in the end, you might consider give
me svn access (I'm writing from my SF email), as I'm doing this also for
the linkstationwiki project at SF... But beware, I'm also very short on
spare time :-)

For svn access, you can ask on the synce-devel mailing list. (I can't
actually provide it for you!) But go for it, if you think you're able.
If you know a bit about repoman and EAPI's then I think you know enough!

- I reduced the packages and USE flags to the current packages and left
out the obsoleted ones (I talked with Jc2k which ones to keep).
- new Documentation dir, as seen in other overlays, containing also
some keywording and portage set files (for portage-2.2 you know)
- I removed the the keywords of the 9999 ebuilds I touched myself, have
a look at the keywords file in the doc dir how to handle those with new
portage
- I don't know if what I did in the synce-gvfs-9999.ebuild breaks any
portage rules by building another package (as it is needed at build
time), but it works :-)
- for most of them I removed the manifest files before diff, you'll
have to re-create them...
Have fun,
Lucian (aka Zoolooc)

thanks!