On Sun, Nov 30, 2008 at 8:53 AM, Peter Volkov <[EMAIL PROTECTED]> wrote: > В Вск, 30/11/2008 в 17:09 +0200, Serkan Kaba пишет: >> Peter Volkov yazmış: >> > Also sometimes it's useful to have different HOMEPAGE for different >> > versions. >> > >> > And in general, Diego. What are you trying to improve with this change? >> > The original intention was to separate common information from all >> > ebuilds into metadata.xml. But obviously, HOMEPAGE changes from ebuild >> > to ebuild. Now if intention is separate some information from ebuild >> > into metadata.xml then, please, tell me what is the criterion for such >> > information? Why not LICENSE? Currently I don't think this change worth >> > our efforts... >> > >> LICENSE should definetely be avoided to be defined per-package. Upstream >> may decide to relicense new version of packages. > > Well, actually the reason we should avoid LICENSES in metadata.xml is > that it's used by portage and possibly at some point of time it'll be > possible to filter packages based on LICENSE. But the general question > still stands: what is the criterion we should use to separate variables > from .ebuild into metadata.xml and what are the benefits of such > separation?
Going to randomly jump in, partially because I have a comment here. Ebuilds are already filterable by license in portage, Marius implemented that a while ago. I'm sure the other package managers have similar filtering abilities. To the general thread: Anecdotal evidence is stupid. No one cares if one of your packages has a different homepage per version. Go scan the tree and show how many packages have this problem and we can at least have useful data then (X% of the tree). Zac, if we ask you to prioritize elibs, how long do you think implementation will take? Diego, What are the concrete benefits of your proposal? All, It is important to note that we are a large diverse group of folks and when you propose global changes you have to be willing to sell your idea to a large number of folks or implement it alone. Coming to a list with no data and no real 'pros/cons' data for your idea isn't not a good way to sell it to anyone. However cool the idea is, it is *never* obvious to everyone. It is never cost free. -Alec > > -- > Peter. > > >
