On Thu, 13 Nov 2008 19:20:11 +0100, "Jan-Simon Möller" 
wrote:

>Am Donnerstag 13 November 2008 18:53:59 schrieb John Kelly:
>> Hi,
>> 
>> I want to build my own minimal server distro.  I only use the web
>> client so far.
>> 
>> In my home project, I individually linked each package in Base:build,
>> one by one (very tedious!), until I had all 78 packages.  After a long
>> time, they all built.
>Yes,its very tedious and unnecessary - DON'T DO THIS!
>> The tutorial mentions aggregate vs. link, but I could not see how to
>> link a whole project using the web client.
>If you want to use a whole project as base for your own packages, add it as repository!
>Thats how is it done for all projects (openSUSE:11.0, openSUSE:Factory - all are projects).
>Then _your_ project has a repository derived/on top of e.g. Base:build.
>So the easy way would be:
>* remove all the Base:build packages
>* hit "Add Repository" ind your home and on the next page "[Advanced]"
>* there you can select Base:Build as repository.
>* now add your own packages to your home: - they will be build using the stuff from Base:Build.
>
>> Anyone have suggestions for how to construct a minimal server distro,
>> with compiler and basic dev tools, tracking factory and/or the latest
>> stable release?
>That's the way for factory (Base:Build).
>
>Please keep in mind: every duplicate package is wasting space and cpu-cycles.
>If you just import packages, but have no patch or other changes, use _aggregate.
>If there's no change, why it should get rebuilt ? (Thats what _link would do.)
>
>Overall - what do you want to do exactly ? Please describe - there might be an even easier way.

OK, thanks for the hint about using Base:build as a repo.  I did not
understand that was possible.

What I want to do is, build a very small server distro with as few
base packages as possible.  However, maybe I also want to tweak some
of the base packages -- I'm not sure yet.

But most of all, I want it to be small.  I will add my own local
customization primarily in /usr/local from upstream and homegrown
source tarballs, not rpm packages from the build service.

I put many things in /usr/local because I make various local source
hacks to integrate billing and other systems, and my hacks are useless
outside any environment except my own.

I could build my own complete distro from upstream source tarballs,
and I've done some experimental work towards that, but since others
have already done much collective work on the suse base distro, why
not benefit from their efforts?


-- 
Webmail for Dialup Users
http://www.isp2dial.com/freeaccounts.html
 
-- 
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hi, Op Thursday 13 November 2008 19:20:11 schreef Jan-Simon Möller:

...

The tutorial mentions aggregate vs. link, but I could not see how to link a whole project using the web client.

If you want to use a whole project as base for your own packages, add it as repository! Thats how is it done for all projects (openSUSE:11.0, openSUSE:Factory - all are projects). Then _your_ project has a repository derived/on top of e.g. Base:build. So the easy way would be: * remove all the Base:build packages * hit "Add Repository" ind your home and on the next page "[Advanced]" * there you can select Base:Build as repository. * now add your own packages to your home: - they will be build using the stuff from Base:Build.

2 questions related to this: - Am I correct that it is only possible to add 1 openSUSE version at a time? So if I want to provide multiple repositories e.g. 10.3, 11.0 and factory, this method has to be executed 3 times, is it indeed like this? - Is it only possible to include (build against) 1 other repository? If I want to build against (include) 2 other repositories (like e.g. the hypothetical repositories devel:lang:perl and devel:lang:php), what would be the best method? - build against (e.g.) devel:lang:perl and aggregate the php ones (or the other way around - or just aggregate both - something else?

Please keep in mind: every duplicate package is wasting space and cpu-cycles. If you just import packages, but have no patch or other changes, use _aggregate. If there's no change, why it should get rebuilt ? (Thats what _link would do.)

Because of the confusing comment on the wiki http://en.opensuse.org/Build_Service/Tips_and_Tricks#The_difference_between_... "Aggregate is possible, but slows down your build and requires double space. Better build directly against the other repository." I don't use aggregate.... Is the comment correct, about the slower builds and double file space???? As the packages are already build, I would expect that aggregated are not build at all. Is the table perhaps missing a row with "build against other repository" or if this is possible, build against multiple repositories? -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Donnerstag 13 November 2008 20:38:42 Richard Bos wrote:

Op Thursday 13 November 2008 20:16:48 schreef Richard Bos:

...

...

* now add your own packages to your home: - they will be build using the stuff from Base:Build.

2 questions related to this: - Am I correct that it is only possible to add 1 openSUSE version at a time?   So if I want to provide multiple repositories e.g. 10.3, 11.0 and factory, this method has to be executed 3 times, is it indeed like this?

- Is it only possible to include (build against) 1 other repository?  If I want to build against (include) 2 other repositories (like e.g. the hypothetical repositories devel:lang:perl and devel:lang:php), what would be the best method?   - build against (e.g.) devel:lang:perl and aggregate the php ones (or the other way around   - or just aggregate both   - something else?

Hmmm, while reading this http://en.opensuse.org/Build_Service/Tips_and_Tricks#Adding_multiple_reposi tories_to_a_project would the following work for me: # osc meta -e prj <project name>

and add the 2 lines with repository="openSUSE_11.0" to the project data, like this: <repository name="openSUSE_11.0">

You should not add the following line, because it will be anyway followed to this one from the others. But if you add it here, packages with the same name are taken from here instead from the other projects. This could lead to an incompatible mix of binaries:

<path project="openSUSE:11.0" repository="standard"/>

<path project="server:php:applications" repository="openSUSE_11.0"/> <path project="devel:languages:perl" repository="openSUSE_11.0"/> <arch>i586</arch> <arch>x86_64</arch> </repository>

-- Richard Bos We are borrowing the world of our children, It is not inherited from our parents.

-- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Donnerstag 13 November 2008 20:16:48 Richard Bos wrote:

Hi,

Op Thursday 13 November 2008 19:20:11 schreef Jan-Simon Möller: ....

...

Please keep in mind: every duplicate package is wasting space and cpu-cycles. If you just import packages, but have no patch or other changes, use _aggregate. If there's no change, why it should get rebuilt ? (Thats what _link would do.)

Because of the confusing comment on the wiki http://en.opensuse.org/Build_Service/Tips_and_Tricks#The_difference_between __link_and__aggregate "Aggregate is possible, but slows down your build and requires double space. Better build directly against the other repository." I don't use aggregate.... Is the comment correct, about the slower builds and double file space???? As the packages are already build, I would expect that aggregated are not build at all.

Yes, it is correct. If you do not want to copy it than do not aggregate ;) But just build against the other repository as suggested. ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org