Zac Medico wrote:
>> I propose support for license groups in ebuilds then, I guess.
>
> That seems like a reasonable solution. So, an ebuild can do
> something like LICENSE="@GPL-2+" and that will expand to whatever
> the definition of the GPL-2+ license group happens to be. When a new
> version o
Ciaran McCreesh wrote:
> Sure. Just periodically fetch the repository centrally. Have a master
> list of sync URLs with expected repository names, and use that to
> generate the full master list that includes metadata.
>
> Added bonus: you can quickly remove any repository that no longer
> exists.
On Wed, 30 Sep 2009 18:00:13 +0200
Sebastian Pipping wrote:
> Ciaran McCreesh wrote:
> > On Wed, 30 Sep 2009 17:51:02 +0200
> > Sebastian Pipping wrote:
> >> At the moment moving overlay meta info into the overlays does not
> >> seem like a good idea to. It would mean that any script working
> >
Ciaran McCreesh wrote:
> On Wed, 30 Sep 2009 17:51:02 +0200
> Sebastian Pipping wrote:
>> At the moment moving overlay meta info into the overlays does not seem
>> like a good idea to. It would mean that any script working with
>> overlays needs to check the repo out to get to that data. That
>>
Fabian Groffen wrote:
> Point remains that it looks in-consistant, for repo, name is an
> attribute, while for owner it is a sub-element. Why having attributes
> in the first place anyway?
It's closer to the original layman-global.txt which also makes the
converter scripts simpler (and faster) th
On Wed, 30 Sep 2009 17:51:02 +0200
Sebastian Pipping wrote:
> At the moment moving overlay meta info into the overlays does not seem
> like a good idea to. It would mean that any script working with
> overlays needs to check the repo out to get to that data. That
> doesn't sound like fun to me.
Ciaran McCreesh wrote:
> On Mon, 28 Sep 2009 20:23:34 +0200
> Sebastian Pipping wrote:
>> Now please ask questions and let us know what you think.
>
> Here's an alternative idea:
>
> * Move the repository information into the overlays themselves. Require
> overlays to provide a file containing
On 30-09-2009 17:36:47 +0200, Sebastian Pipping wrote:
> Tiziano Müller wrote:
> > Am Montag, den 28.09.2009, 20:23 +0200 schrieb Sebastian Pipping:
> >> repositories.xml
> >> =
> >>>> name="sping"
> >> quality="exp
Tiziano Müller wrote:
> Am Montag, den 28.09.2009, 20:23 +0200 schrieb Sebastian Pipping:
>> repositories.xml
>> =
>> > name="sping"
>> quality="experimental"
>> status="unofficial">
>> Gentoo overlay of Seb
On Mon, 28 Sep 2009 20:23:34 +0200
Sebastian Pipping wrote:
> Now please ask questions and let us know what you think.
Here's an alternative idea:
* Move the repository information into the overlays themselves. Require
overlays to provide a file containing the description, homepage,
owner in
Am Montag, den 28.09.2009, 20:23 +0200 schrieb Sebastian Pipping:
> repositories.xml
> =
> name="sping"
> quality="experimental"
> status="unofficial">
> Gentoo overlay of Sebastian Pipping
> http://git
11 matches
Mail list logo
