On Monday 25 May 2009, [email protected] wrote: > On Mon, May 25, 2009 at 3:43 PM, Alex Legler <[email protected]> wrote: > > On So, 2009-05-24 at 20:04 +0200, [email protected] wrote: > >> [...] > >> > >> >> app-admin/equo (sabayon overlay -- Entropy Framework client) > >> >> supports the postfix "@repository" to let users force the > >> >> installation of a package from a specific repository. > >> > > >> > @ is used by Portage for sets. Paludis has been using ::repo for > >> > repo dependencies for years. Why not go with the established > >> > syntax? > >> > >> I wrote "postfix" not "prefix". Sets use "@" prefix. > > > > Your @ is still a prefix for the repository name. > > Yeah but "emerge @overlay" would be obviously illegal. So your > argument is a bit pointless ;)
# emerge --update lsof @system versus # emerge --update l...@system would have completely different meanings. This is what I would dislike about the '@' character. I'm ok with :: though. If we use repo_name as the overlay identifier, we must rethink how layman-global.txt is currently handled. Many overlays in there have that file missing, and some have different identifiers than what layman displays as their name. Is this specifier stored and considered on future dependency calculations (e.g. updates, dependencies of other ebuilds on the package that was installed via @overlay)? Where is it stored, how is it displayed to the user in emerge/eix output? Robert
signature.asc
Description: This is a digitally signed message part.
