the gensync application from gentoolkit-dev includes configuration files to access and work with the breakmygentoo project (in /etc/gensync), although there's no problem with this function, the configuration files supplied with a gentoo utility might be considered an endorsement.
several threads on gentoo-dev have indicated that most developers feel endorsing or even mentioning bmg should be avoided.
How about removing the configuration files, and replacing them with generic alternatives? instead of breakmygentoo.org, myportageserver.com and instead "BreakMyGentoo main tree" and "BreakMyGentoo GNOME current", how about "My Portage Ebuilds" or something...if users want to use bmg, they can just fill in the blanks.
$ ls /etc/gensync
bmg-gnome-current.syncsource bmg-main.syncsource gensync.conf
Hopefully, future versions of Portage will attach a 'tainted' flag to non-Gentoo
ebuilds, as discussed elsewhere.
However, I guess I should add a prominent warning that merging any package from
*ANY* overlay is grounds for dismissal on bugs.gentoo.org.
I will take a closer look.
Perhaps WONTFIX this?
Does anyone have any objections to deprecating gensync in favor of app-portage/layman?
*** Bug 160026 has been marked as a duplicate of this bug. ***
My bug wasn't really a duplicate -- this bug complains about *endorsement* of BMG, whereas mine complains about having *any* syncsources shipped.
I will repeat my question:
(In reply to comment #5)
> Does anyone have any objections to deprecating gensync in favor of
just do it baby
Not sure, here's what I need:
- an ebuild I can depend on which provides the sync utility
- the ability to install a number of sync sources from another ebuild (e.g. putting files in /etc/gensync/)
- a short command which will update from ALL of my sync sources *but no others* which might or might not be installed along with the sync util
> Not sure, here's what I need:
> - an ebuild I can depend on which provides the sync utility
app-portage/layman is in active development and maintained by wrobel. It supports the following protocols for syncing overlays: rsync, subversion, bzr, darcs, git, mercurial, or tar
> - the ability to install a number of sync sources from another ebuild (e.g.
> putting files in /etc/gensync/)
layman uses an XML file to define the sync sources. The master is maintained at http://www.gentoo.org/proj/en/overlays/layman-global.txt You can also define and use your own files. So an ebuild could install a sync sources file somewhere that can then be read by layman.
> - a short command which will update from ALL of my sync sources *but no
> others* which might or might not be installed along with the sync util
After defining the sync sources, you tell layman to add the overlays that you want to use. After that running layman --sync ALL will sync just those overlays and nothing else.
I would highly recommend talking a look at it. For now though, I'm planning on removing gensync from gentoolkit-dev
Thanks, layman does what I need it to.
gensync has been deprecated in gentoolkit-dev-0.2.6.2 and will be completely removed in the next version.