Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
Sebastian Pipping wrote: Robert Buchholz wrote: 1. has no DTD/xml validation schema I'd like to be part of the schema creation process [..] First try on a DTD and Relax NG schema for Layman's current overlays.xml format (used in layman-global.txt) over here: http://git.goodpoint.de/?p=overlays-xml-specification.git Feedback welcome. Sebastian
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
On 15:53 Sun 12 Jul , Sebastian Pipping wrote: The output produces line like MISMATCH gentoo-china (layman-global) versus china (repo_name) I have just changed gentoo-china overlay's repo_name to gentoo-china. -- Zhang, Le Gentoo/Loongson Developer http://zhangle.is-a-geek.org 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 pgpohUiov0DfE.pgp Description: PGP signature
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
On Sonntag, 12. Juli 2009, Sebastian Pipping wrote: vdr-xine-overlay, # vdr-xine Fixed to be vdr-xine. Zzam
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
Fabian Groffen wrote: So alternative, what if we extend the layman-global.txt (which is xml in reality...) file with an extra property per overlay which holds the contents of it's repo_name? Good idea. I'll try to create a map for all overlays in layman-global.txt as a next step. Layman and shell tools should help with that. Sebastian
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
Sebastian Pipping wrote: I'll try to create a map for all overlays in layman-global.txt as a next step. Layman and shell tools should help with that. Believe it or not: discs space issues disallow me to have an answer already. The code is there, I just cannot checkout all overlays at the same time :-( Maybe anybody else could run below commands before I find time to fix the disc space thing. High level view: - Checkout the mismatch detector script - Backup the set of names of your current overlays - Add all overlays - Run the script - Remove all overlays - Restore the set of original overlays Low level view: # git clone git://git.goodpoint.de/smolt-gentoo.git # cd smolt-gentoo # git checkout -b gentoo origin/gentoo # cd client/distros/gentoo # layman -l my_active_overlays.txt # sudo layman -f # sudo layman -a ALL # python _mismatch.py | tee repo_name_analysis.txt # sudo layman -d ALL # sed 's|^[^ ]* \([^ ]\+\).*$|\1|' my_active_overlays.txt | \ xargs -n 1 sudo layman -a The output produces line like MISMATCH gentoo-china (layman-global) versus china (repo_name) Please share the resulting repo_name_analysis.txt with us. I guess it all sounds a bit odd, but maybe it's fun to you and we have an answer faster. I have 17 mismatches here already. Sebastian
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
On Sunday 12 July 2009, Fabian Groffen wrote: since I assume you can't reliably use the checked out version of the overlay (by e.g. layman), can you try to retrieve the repo_name file from the overlay? Probably a lot of efforts. So alternative, what if we extend the layman-global.txt (which is xml in reality...) file with an extra property per overlay which holds the contents of it's repo_name? Would be optimal, since you're fetching this file anyway to check it. Alternative is to use another file somewhere on the interweb that you keep up to date automatically, by having all overlays checked out and recording their repo_name ... I think it should be a requirement that repo_name == layman name for an overlay to be added to layman. If that file changes later, we should see a warning *somewhere*. It is a perfect opportunity to revisit the overlays+metadata cache idea presented by patrick a while ago (and do other overdue changes!). Since writing down stuff into an IDEAS file in my $HOME does not get anything implemented, and I'm still looking for a way to have a wiki-like lightweight GLEP (which I prefer for collecting ideas), here's what I have so far: Background: Overlays are useful, fast-moving playground for inclusion of new ebuilds and distributed community effort. layman-global.txt is the central list of overlays Issues: 1. In layman-global.txt: 1. has no DTD/xml validation schema 2. overlays have only a contact address, no real name 3. overlay name in xml file might not be overlay's repo_name 4. Exactly one overlay URL, no mirrors possible 2. overlays.g.o website: 1. Feed is out of date 2. Only lists dev and proj overlays, not third-party 3. Has no overlay content index 4. Has no overlay search 3. Overlays do not have metadata 4. Overlays are not natively supported by package manager, but through an external app and a 'source' in make.conf Ideas: 1. Revamp layman-global.txt, keep it as authority file: 1. Move file to overlays.xml (but keep a compatibility copy) 2. Create XML DTD/schema to make it validatable 3. Change 'official' attribute to differentiate between 'dev', 'proj' and '3rdparty/unofficial' 4. Add value for overlay RSS feed if available 5. Add real name for owner 6. Have multiple overlay URIs with checkout priorities 2. Write script to generate planet config from overlays.xml 3. Have copies of the overlays on official gentoo.org infra, generate metadata for them and export them via rsync (the bonsaikitten proposal at http://thread.gmane.org/gmane.linux.gentoo.devel/62025/ ) 4. Validate repo_name vs. XML file (needs 3.) 5. Move search and browse features to overlays.g.o website, see: 1. http://git.exherbo.org/summer/ 2. http://gpo.zugaina.org/ 3. http://gentoo-overlays.zugaina.org/ 6. Extend layman to use one of many overlay URIs or allow user select Robert signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
Robert Buchholz wrote: 1. has no DTD/xml validation schema I'd like to be part of the schema creation process but feel that having pre-mature schema's on the list and it's archives is not a good idea. If we had a schema file: where would we store it? Sebastian
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
On Sunday 12 July 2009, Sebastian Pipping wrote: Robert Buchholz wrote: 1. has no DTD/xml validation schema I'd like to be part of the schema creation process but feel that having pre-mature schema's on the list and it's archives is not a good idea. It's probably wise not to discuss the specifics of that file on this list, but keep experimentation in a smaller group. I wonder if a new mailing list is needed or whether we just do this over the overlays alias. If we had a schema file: where would we store it? Possibly here: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/dtd/ Robert signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [rfc] repo_name/layman-global.txt overlay name mismatches
So here's the current result of my analysis: == Format: repo_name, # layman-global.txt Entries: maekke's overlay, # maekke kde, # kde-testing ERROR: Overlay lordvan lacks repo_name entry ERROR: Overlay rox lacks repo_name entry ERROR: Overlay rion lacks repo_name entry ERROR: Overlay gnash-cvs lacks repo_name entry ERROR: Overlay php-4 lacks repo_name entry ERROR: Overlay rostov lacks repo_name entry ERROR: Overlay roslin lacks repo_name entry ERROR: Overlay postgresql-testing lacks repo_name entry ERROR: Overlay pd-overlay lacks repo_name entry geki-overlay, # openoffice-geki mpd-portage, # mpd tante_overlay, # tante ERROR: Overlay stuart-desktop lacks repo_name entry ERROR: Overlay d lacks repo_name entry gentoo-lisp-overlay, # lisp ERROR: Overlay chtekk-syscp lacks repo_name entry soor, # soor-overlay dev-jokey, # jokey Falco's git overlay, # falco kde4-experimental, # kde ERROR: Overlay hanno-xgl lacks repo_name entry ERROR: Overlay sipx lacks repo_name entry ERROR: Overlay cell lacks repo_name entry ERROR: Overlay pchrist lacks repo_name entry digital-trauma.de, # trauma ERROR: Overlay genscripts lacks repo_name entry ERROR: Overlay powerpc lacks repo_name entry gcj-overlay, # java-gcj-overlay steev_github, # steev pcsx2-overlay, # pcsx2 vdr-xine-overlay, # vdr-xine china, # gentoo-china ERROR: Overlay marineam-xen lacks repo_name entry gentoo-haskell, # haskell ERROR: Overlay openmoko lacks repo_name entry ERROR: Overlay tove lacks repo_name entry ERROR: Overlay stuart-server lacks repo_name entry ERROR: Overlay deathwing00 lacks repo_name entry ERROR: Overlay trapni lacks repo_name entry ERROR: Overlay gnr lacks repo_name entry webapp-experimental, # webapps-experimental ERROR: Overlay eclipse lacks repo_name entry proaudio, # pro-audio ERROR: Overlay seemant lacks repo_name entry ERROR: Overlay pythonhead lacks repo_name entry ERROR: Overlay initng lacks repo_name entry ERROR: Overlay gentoojp not found majeru, # oss-overlay ERROR: Overlay plan9 lacks repo_name entry ERROR: Overlay m68k lacks repo_name entry ERROR: Overlay iwlwifi lacks repo_name entry bangert-ebuilds, # bangert suka's dev overlay - experimental stuff of all sorts, # suka ERROR: Overlay stuart-perforce lacks repo_name entry ERROR: Overlay break-my-gentoo-main lacks repo_name entry ERROR: Overlay ramereth lacks repo_name entry leio-personal, # leio ERROR: Overlay aross lacks repo_name entry ogo-lu_zero, # lu_zero ERROR: Overlay mysql-testing lacks repo_name entry scarabeus_local_overlay, # scarabeus ERROR: Overlay liquidx lacks repo_name entry ERROR: Overlay lila-theme lacks repo_name entry == That means quite a lot to do. Shall I make the script send e-mails to the overlay contacts? :-) I have added the mismatched repo_names to a whitelist in Gentoo Smolt, so packages installed before a repo_name fix should be collectable, too. Sebastian
