Mailinglist Archive: opensuse-buildservice (213 mails)

< Previous Next >
Re: [opensuse-buildservice] Why is an empty linked package an error?
  • From: Luke Imhoff <luke@xxxxxxxx>
  • Date: Tue, 30 Jun 2009 15:15:48 -0500
  • Message-id: <4A4A7274.8070102@xxxxxxxx>
Adrian Schröter wrote:
Am Montag, 29. Juni 2009 21:26:12 schrieb Luke Imhoff:
Why does OBS consider an empty linked package an error? If I can check
out an empty package to upload source, why I can't I checkout a link to
that package and expand it to an empty directory? This comes up for our
internal use cases where a developer wants to check that a new package
builds in all the distros that are going to link in the package before
checking it in. Right now they have to upload some file to the linked
to package first so the linking package can be checked out to do an osc
build locally. This is more a design philosophy question as I can
easily change osc to ignore the error (or change the server to not treat
it as a error).

Actually it just sounds like a bug. If you have an osc patch to solve this, I am happy to apply that one.
Actually, there are multiple places where this could be 'fixed'. It's bs_srcserver that first generates the empty error, so I was wonder if it'd be more correct to fix it there or to fix it on the frontend or, like I had originally thought, to fix it just in osc. I wasn't sure if returning nothing/an empty directory would be handled correctly from the srcserver up through the frontend and finally osc. I was hoping someone on the list could point out any problems I could hit fixing it in bs_srcserver that aren't immediately obvious.
thanks
adrian

It just seems that if you think of the link as a
symlink (with versioning) to a directory then you should be able to
checkout an empty directory just the same as a directory with contents.

yes

Am I missing something in the design that makes this analogy not accurate?


--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >