Mailinglist Archive: opensuse-buildservice (181 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] More buildservice questions
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Tue, 31 Jul 2007 11:05:12 +0200
- Message-id: <200707311105.12822.adrian@xxxxxxx>
On Tuesday 31 July 2007 10:09:15 wrote Paul Elliott:
> I have some more build service questions:
>
> (1) On my create home project page, it says:
>
> Please ask on opensuse-buildservice@xxxxxxxxxxxx mailing list
> before creating projects outside of your home:<login>
> namespace.
hm, a bit obsolete wrong text meanwhile .. fixing ...
> So does this mean that you can create subprojects of your
> home:<login> namespece? How deep can subprojects be nested?
Today, you can't create projects outside of namespaces where you have write
permissions. This is by default only home:<user>. I think we have no limit of
deepness, at least no one reached it until now ;)
> The feature we were discussing yesterday:
> <publish>
> <disable />
> </publish>
> Can that be per sub-project, so that you can have some public
> subprojects and some private?
For every project, there is nothing like a sub-project only projects which are
beyond your name spaces. But home:a:x has nothing todo with home:a, except
that you were allowed to create it.
> (2) On the Workflows page:
>
> Edit Packages
> add files
> add sources (http source, svn/cvs source)
> edit spec file (using web ui)
> add/remove users
> change version
>
> What is the difference between a source and a file?
hm, I think not much anymore, we store a different classification in the
database, but I think we do not use it somewhere ...
> Can a source be a FQDN like source0 in a spec file?
Yes, but the build host will not download it, because it has no access to the
internet. So you need to submit the tar ball together with the spec file
anyway.
> Explain what svn/cvs source is like. Does it have to refer
> to the buildservce svn/cvs?
no, the buildservice svn is where we work on the code for the build service
system. An svn/cvs source is a remote svn/cvs repo which can be handled by
the build service. This means you can specify how to download/checkout the
source and to package the tar ball for building.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
> I have some more build service questions:
>
> (1) On my create home project page, it says:
>
> Please ask on opensuse-buildservice@xxxxxxxxxxxx mailing list
> before creating projects outside of your home:<login>
> namespace.
hm, a bit obsolete wrong text meanwhile .. fixing ...
> So does this mean that you can create subprojects of your
> home:<login> namespece? How deep can subprojects be nested?
Today, you can't create projects outside of namespaces where you have write
permissions. This is by default only home:<user>. I think we have no limit of
deepness, at least no one reached it until now ;)
> The feature we were discussing yesterday:
> <publish>
> <disable />
> </publish>
> Can that be per sub-project, so that you can have some public
> subprojects and some private?
For every project, there is nothing like a sub-project only projects which are
beyond your name spaces. But home:a:x has nothing todo with home:a, except
that you were allowed to create it.
> (2) On the Workflows page:
>
> Edit Packages
> add files
> add sources (http source, svn/cvs source)
> edit spec file (using web ui)
> add/remove users
> change version
>
> What is the difference between a source and a file?
hm, I think not much anymore, we store a different classification in the
database, but I think we do not use it somewhere ...
> Can a source be a FQDN like source0 in a spec file?
Yes, but the build host will not download it, because it has no access to the
internet. So you need to submit the tar ball together with the spec file
anyway.
> Explain what svn/cvs source is like. Does it have to refer
> to the buildservce svn/cvs?
no, the buildservice svn is where we work on the code for the build service
system. An svn/cvs source is a remote svn/cvs repo which can be handled by
the build service. This means you can specify how to download/checkout the
source and to package the tar ball for building.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |