fedora non-released buildsys
 

Hi,
A few of us have been working on the basis for a buildsystem for fedora
for our non-released pkgs. This is ultimately for building ad-hoc stacks
of packages from both trusted and untrusted repos.


Use cases:
- personal repos (coprs)
- ad-hoc language-module repos (ruby, python, cpan, etc) for people who
need infinite versions of every module compiled against all of the other
possible permutations

- fail to be build from source rebuild runs.
- other ideas here.

Some discussion of it is here:
https://fedoraproject.org/wiki/User:Skvidal/BuildSystem

we've been meeting in #fedora-buildsys on freenode - though that's mostly
quiet right now.


When last this was discussed the koji maintainers were fairly
adamant that the above use cases was definitely outside
of the scope and goals of koji (which is entirely appropriate given what
koji does and how it does it). I was asked to reconfirm that so I am
doing it now.


I'm also letting people know that this is going on and if they want to
join in, please do so. :)


-sv

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 1 Oct 2012 08:57:18 -0400 (EDT)
Seth Vidal <skvidal@fedoraproject.org> wrote:

> Hi,
> A few of us have been working on the basis for a buildsystem for
> fedora for our non-released pkgs. This is ultimately for building
> ad-hoc stacks of packages from both trusted and untrusted repos.
>
> Use cases:
> - personal repos (coprs)
> - ad-hoc language-module repos (ruby, python, cpan, etc) for people
> who need infinite versions of every module compiled against all of
> the other possible permutations
> - fail to be build from source rebuild runs.
> - other ideas here.
>
> Some discussion of it is here:
> https://fedoraproject.org/wiki/User:Skvidal/BuildSystem
>
> we've been meeting in #fedora-buildsys on freenode - though that's
> mostly quiet right now.
>
> When last this was discussed the koji maintainers were fairly
> adamant that the above use cases was definitely outside
> of the scope and goals of koji (which is entirely appropriate given
> what koji does and how it does it). I was asked to reconfirm that so
> I am doing it now.
>
> I'm also letting people know that this is going on and if they want
> to join in, please do so. :)

Im definetly interested in keeping in the loop here. yes it is outside
the scope fo koji, you could be asked to build the same nvr multiple
times in different buildroots, build the same nvr in the FTBFS case, I
really do not see it fitting in at all with koji's goals.

you may be able to kludge it into koji with external repos and scratch
builds but it is pretty kludgy.

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlBp9yAACgkQkSxm47BaWferbwCgwctQdqQmor APgJpVZTXG+fGa
3aYAoIwqf9dEEmZEbGL+CBt5b3lZg+Qs
=zjtt
-----END PGP SIGNATURE-----
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

----- Original Message -----
> Hi,
> A few of us have been working on the basis for a buildsystem for
> fedora
> for our non-released pkgs. This is ultimately for building ad-hoc
> stacks
> of packages from both trusted and untrusted repos.
>
> Use cases:
> - personal repos (coprs)
> - ad-hoc language-module repos (ruby, python, cpan, etc) for people
> who
> need infinite versions of every module compiled against all of the
> other
> possible permutations
> - fail to be build from source rebuild runs.
> - other ideas here.
>
> Some discussion of it is here:
> https://fedoraproject.org/wiki/User:Skvidal/BuildSystem
>
> we've been meeting in #fedora-buildsys on freenode - though that's
> mostly
> quiet right now.
>
> When last this was discussed the koji maintainers were fairly
> adamant that the above use cases was definitely outside
> of the scope and goals of koji (which is entirely appropriate given
> what
> koji does and how it does it). I was asked to reconfirm that so I am
> doing it now.
>
> I'm also letting people know that this is going on and if they want
> to
> join in, please do so. :)
>
> -sv
>
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

Hi all,
since I'm also involved in this, here is something from me :)
I've put together some preliminary specification, it is available at [1]. I'll be very glad if anyone who is interested looks at it and makes suggestions/proposes corrections.
BTW, so far we're calling this project BuildSys/PrivateRepos, but we may also need a better name...

Slavek.

--
Regards,
Bohuslav "Slavek" Kabrda.

[1] https://fedoraproject.org/wiki/User:Bkabrda/BuildSys
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

Bohuslav Kabrda wrote:
> BTW, so far we're calling this project BuildSys/PrivateRepos, but we may also need a better name...

This project sounds very similar to Ubuntu PPA repos. IMHO we should
call it the same thing.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

On Tue, 2 Oct 2012, Michael Cronenworth wrote:


Bohuslav Kabrda wrote:

BTW, so far we're calling this project BuildSys/PrivateRepos, but we may also need a better name...


This project sounds very similar to Ubuntu PPA repos. IMHO we should
call it the same thing.


I disagree for the following reasons:
1. Calling it the same thing implies feature parity which is NOT
something we are interested in.
2. Ditto it just causes people to draw unnecessary comparisons which just
makes our task more difficult


-sv

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

----- Original Message -----
> Bohuslav Kabrda wrote:
> > BTW, so far we're calling this project BuildSys/PrivateRepos, but
> > we may also need a better name...
>
> This project sounds very similar to Ubuntu PPA repos. IMHO we should
> call it the same thing.

Yep, it is very similar - but wouldn't calling it the same cause some legal questions/issues? I think that the safest way would be creating a name and then consulting people from legal, so that we don't get into any kind of trouble.

> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

--
Regards,
Bohuslav "Slavek" Kabrda.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

Seth Vidal wrote:
> A few of us have been working on the basis for a buildsystem for fedora
> for our non-released pkgs. This is ultimately for building ad-hoc stacks
> of packages from both trusted and untrusted repos.
>
> Use cases:
> - personal repos (coprs)
> - ad-hoc language-module repos (ruby, python, cpan, etc) for people who
> need infinite versions of every module compiled against all of the other
> possible permutations
> - fail to be build from source rebuild runs.
> - other ideas here.
>
> Some discussion of it is here:
> https://fedoraproject.org/wiki/User:Skvidal/BuildSystem

How are you going to keep out non-free packages?
eg: NVIDIA driver or Flash
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

On Tue, 2 Oct 2012, Michael Cronenworth wrote:


Seth Vidal wrote:

A few of us have been working on the basis for a buildsystem for fedora
for our non-released pkgs. This is ultimately for building ad-hoc stacks
of packages from both trusted and untrusted repos.

Use cases:
- personal repos (coprs)
- ad-hoc language-module repos (ruby, python, cpan, etc) for people who
need infinite versions of every module compiled against all of the other
possible permutations
- fail to be build from source rebuild runs.
- other ideas here.

Some discussion of it is here:
https://fedoraproject.org/wiki/User:Skvidal/BuildSystem


How are you going to keep out non-free packages?
eg: NVIDIA driver or Flash


by checking the license field of the spec file and assuming that the users
are not lying.



if they do lie then I think the course of action is obvious.

-sv

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

On Tue, Oct 2, 2012 at 9:19 AM, Seth Vidal <skvidal@fedoraproject.org> wrote:
> by checking the license field of the spec file and assuming that the users
> are not lying.
>
> if they do lie then I think the course of action is obvious.
>

I'm not sure it is obvious? People make mistakes, particularly around this area.

- Ken
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

fedora non-released buildsys
 

On Tue, 2 Oct 2012, Ken Dreyer wrote:


On Tue, Oct 2, 2012 at 9:19 AM, Seth Vidal <skvidal@fedoraproject.org> wrote:

by checking the license field of the spec file and assuming that the users
are not lying.

if they do lie then I think the course of action is obvious.



I'm not sure it is obvious? People make mistakes, particularly around this area.



If someone is lying or mistaken we pull the files.

That's the obvious response.

Mistakes happen, if someone does it repeatedly despite warnings then we
talk to the Powers_That_Be b/c they've violated their fedora account
agreement.


-sv

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys