I am trying to compile some packages against the $SUBJECT repository,
and there are some missing dependancies. From my previous post,
I gather that the best overall solution is to push for continued expansion
of that repository.
Would the maintainers of $SUBJECT repository be kind enough
to add: tetex, texinfo, tck, tk ?
Thanks!
- Jay Migliaccio
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
Just a small comment about the new WebGui for the BS: I think the icon
next to the text 'Build Status' (the icon looks like a 'refresh').
I expected it more to 'refresh' the view of the build status than to
trigger a rebuild (ok: I didn't have to click.. the hover text was clear
then).
The 'Involved users' is a very nice thing and looks promising for
future releases to find all your packages, as spread as they are over
the BuildService. How evolved are the ideas of what should be able to
find / monitor using the 'involved users' ?
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
api.opensuse.org is now able to search in project and package metadata using a
xpath-like syntax.
Following GET requests have been added:
/search/project?match=<predicate>
/search/project/id?match=<predicate>
/search/package?match=<predicate>
/search/package/id?match=<predicate>
Result documents are put into a <container></container> node. The paths ending
on /id return only the root node of the wanted metafile type, which speeds up
the request a lot. The other paths return the whole documents.
The match parameter is mandatory and specifies the predicate used to select
the wanted metafiles.
Not the whole xpath specification is supported, we only support a subset of
operators and functions, and only specific node tests.
Allowed node tests for projects:
@name
description
title
person/@userid
repository/path/@project
Allowed node tests for packages:
@name
@project
title
description
person/@userid
Allowed operators:
=
!=
and
or
Allowed functions:
not(expr)
contains(string,substring)
starts-with(string,substring)
ends-with(string,substring)
Examples:
/search/package/id?match=person/@userid='darix'
returns the root nodes of all package metafiles where darix is set as
maintainer
/search/project/id?match=starts-with(@name,'SUSE:')
returns the metafiles of all projects below the SUSE: namespace
/search/project/id?match=ends-with(@name,person/@userid)
returns the root nodes of all project metafiles where the project name
ends with the userid of one of the maintainers (that is, all home
projects)
/search/project?match=[not(starts-with(@name,'home'))%20and%20description='']
all projects not under the 'home:' namespace whose description element is
empty
More functions/operators/node tests might get implemented if the need for them
arises.
Happy Holidays
--
Andreas Bauer - Novell - SUSE Internal Tools
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I just read this:
http://ianmurdock.com/?p=388
It's a blog about why software installation sucks on Linux.
He is right with many of his statements, we all experienced
that in the past. Distributions took that job and improved a
lot.
But still there are problems: For ISVs, for organisations who
want to stay distribution independent and for the lots of
developers whos work did not yet make it to a distribution.
It's very much work to maintain all the building instructions
for the various distributions out there in case you just want
to code (and unfortunately people like to use your code) and
your hobby is not packaging. You hardly have a chance to get
many rpms for your project from outside unless it's really
prominent.
That's another area where the buildservice really can make a
difference.
Moreover if we in once can think of a more general build
description - which could be a meta-description of spec files,
we could ease the pain of the people who have to maintain so
many different spec files and others for different platforms.
Since maintaining lots of stuff is a cost factor for ISVs,
I think that would be one additonal argument to port to Linux.
True?
Klaas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
hi,
everything will be build but not synced out to the world.
sadly we cant fix that atm. (broken hardware sucks)
so we have to wait until tomorrow morning european time.
thanks for your patience and thanks for using the buildservice.
with kind regards
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello hackers!
I am working with EDU customers who are standardizing on SLED -
and interested to use some open source applications, on top of SLED.
I have started a Education:desktop project - and am working with them
to build a repository for SLED of applications that they need. Think of
this
as an EDU Desktop Apps Addon CD projects.
The biggest challenge for us - is that some of the packages we
are trying to compile need additional libraries that are not available in
SLED,
or SLE-SDK. Fortunatly some of you have created SLE:SDK:Extras,
but in my case - I need even more libraries than are available in there.
(ie: python-sqlite2<http://build.opensuse.org/package/show?package=python-sqlite2&project=Educa…>
).
Is anyone else hitting that limitation too?
Is it better to get the SLE:SDK:Extras repository extended, or to
create, yet another repository (ie: SDK:Extras:more)?
Suggestions or solutions are welcome.
- Jay Migliaccio
Hi gang,
could somebody explain me the purpose of those "special" revision numbers
currently found in diverse repos, e.g.: KDE3: kdelibs3-3.5.5-.4.i586.rpm -
or even better - fix them up, Adrian?!?
Cheers,
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Thank you for explaining that. Adding repositories should be made easy, but more than that I'd say there should be some page somewhere explaining what these repositories are. Kind like how Joe explained it. Since these repos could be broken etc, we don't want them to be too easy for in-experienced users to add them and break things; but there definitely should be some write up somewhere on what this is all abt. As of now all that there is is that there's the Suse Build Service, and this location here is the repository ..........
Rakhesh
----- Original Message ----
From: Pascal Bleser <pascal.bleser(a)skynet.be>
To: opensuse-buildservice(a)opensuse.org
Sent: Monday, December 11, 2006 8:12:45 PM
Subject: Re: [opensuse-buildservice] Difference between GNOME:Community, Stable, and Unstable
Joe Shaw wrote:
> On Sun, 2006-12-10 at 01:45 -0800, Rakhesh Sasidharan wrote:
>> Also, I find folders for "Archiving:" and "editors" and "Banshee" and
>> so on -- am I supposed to go through each and add them individually as
>> a repo, or is there a single repo or something which sort of includes
>> all these? Why are they classified like these into categories, in the
>> first place? Do I need to add them, or are these just the software
>> that was already installed on my system?
[...]
> There isn't (at present, anyway) an Ubuntuesque concept of a "universe"
> repository, which is more or less a dumping ground for whatever packages
> people want. Although the multiple repositories might be a little
> harder to use(*), it does mean that you get only the software you're
> interested in, and is less likely to break your system.
>
> (*) IMO, it's only harder to use right now because it lacks a search
> interface. Once it has one of those, that lets you search by project
> name, package name, and inside package descriptions, it'll be a whole
> lot easier to find specific pieces of software.
I agree, it is technically superior to the big dumping ground.
Nevertheless, it is a lot less user-friendly, especially for less
experienced users.
One might argue that less experienced users shouldn't touch anything
that's not on the distribution with a stick but reality is different
(and e.g. quickly having the latest KDE packages _does_ provide a
competitive advantage to SUSE Linux IMO).
Searching is one thing, but adding repositories should be made easier
too. A more-or-less one-click-installation for YaST2 would be very
helpful (we already have the .repo files).
Add a MIME type, hook a YaST2 frontend to it in Firefox and Konqueror.
Including .repo links in search results.
my 0.02€
cheers
--
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be>
_\_v http://www.fosdem.orghttp://opensuse.org
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all.
I'm here to request a build service account. As you requested on opensuse.org
here goes some stuffs about me and about what I intend to package:
My name is Carlos Gonçalves and I live in Portugal (yeah, that little European
country forgoten by some). I'm a SUSEPT moderator (¹), a wiki and openSUSE
(distro/software) translator (ah! I'm a Tellico translator too). Also, KDE-PT
co-admin (unreleased community, yet!).
That are basicly my contributions to the open source community.
My account would be to package some unusual/new apps (mostly Kapps - did you
figured out why?! ;-) ) since many apps are already packaged thanks to the
great (open)SUSE packagers we have :-D
To begin and release some RPMs that 'my' SUSEPT community wants, I created a
simple folder in my webhost here I upload my RPMs. You can take a look at
http://www.carlos.pinguix.com/suse/ - as you can see I only can build to SUSE
10.1 and to x86 so that's one more reason to want an account.
Best regards,
Carlos Gonçalves
¹ - Had the idea, together with some SUSEPT users, to mirror build service,
apt, ISOs and official updates. Found a sponsor (to the hard drive) and sent
it to NUX (Instituto Politécnico de Bragança's Linux Group) to host.
Now we are just checking the integrity of the mirror so in a few hours it
will be available.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org