[gentoo-dev] Smalltalk/X

[gentoo-dev] Smalltalk/X

[Marko Mikulicic]

Hello,

I have I little problem creating the .ebuild file for Smalltalk/X.
The creator of that program distributes two packages, one named:
  common.tgz and the other linux.tgz. The version of the package
is contained in the directory. (like: 
http://www.exept.de/download/stx414/common.tgz)

Well, I have wrote the script like:

...
S=${WORKDIR}/stx
A1=common.tgz
A2=linux.tgz
SRC_URI1="http://www.exept.de/download/stx414/${A1}"
SRC_URI2="http://www.exept.de/download/stx414/${A2}"

SRC_URI="${SRC_URI1} ${SRC_URI2}"

DEPEND="virtual/glibc virtual/x11"

#
src_unpack() {
         unpack ${A1}
         unpack ${A2}
}
...

and it works. But it creates linux.tgz and common.tgz in 
/usr/portage/distfiles and what is worse is first try to download
them from the mirror. How can I handle this, writing the fewest possible
hacks?

Thanks

Marko


PS: the software is free for non-commercial use, and probably the vendor 
will not change it's distribution method. Since it's a rare commercial 
product which doesn't require registration in ordere to download, it 
would be sad if user should download it by hand and then
place it in /usr/portage/distfiles with a more appropriate name.

Re: [gentoo-dev] Smalltalk/X

[Karl Trygve Kalleberg]

On Sat, 8 Jun 2002, Marko Mikulicic wrote:

> and it works. But it creates linux.tgz and common.tgz in 
> /usr/portage/distfiles and what is worse is first try to download
> them from the mirror. How can I handle this, writing the fewest possible
> hacks?

We have consciously decided not to handle this particular problem
automatically. What we do is copy the upstream source files, give them
proper names, then put them out directly (manually) on our mirrors.

You should remind the developer who takes care of your ebuild to do
exactly that before committing your ebuild to CVS.

Karl T

Re: [gentoo-dev] Smalltalk/X

[Marko Mikulicic]

Karl Trygve Kalleberg wrote:
> On Sat, 8 Jun 2002, Marko Mikulicic wrote:
> 
> 
>>and it works. But it creates linux.tgz and common.tgz in 
>>/usr/portage/distfiles and what is worse is first try to download
>>them from the mirror. How can I handle this, writing the fewest possible
>>hacks?
>>
> 
> We have consciously decided not to handle this particular problem
> automatically. What we do is copy the upstream source files, give them
> proper names, then put them out directly (manually) on our mirrors.

I don't understand. Does this mean that those packages cannot be
download from the original url but only from your mirror. This
solves a problem, but raises other: if the package is not in the mirrors,
or the mirror is down, or the package is not yet in CVS ?
  This means that while I'm writing the package I cannot test it
completly (at least not the download) until it is copied to the mirrors.
  What SRC_URI should I put in the .ebuild ? Only 
http:/nowhere/${PN}-${PV}.tar.gz ?


Marko

Re: [gentoo-dev] Smalltalk/X

[Defresne Sylvain]

Hello

> I don't understand. Does this mean that those packages cannot be
> download from the original url but only from your mirror. This
> solves a problem, but raises other: if the package is not in the mirrors,
> or the mirror is down, or the package is not yet in CVS ?
>  This means that while I'm writing the package I cannot test it
> completly (at least not the download) until it is copied to the mirrors.
>  What SRC_URI should I put in the .ebuild ? Only 
> http:/nowhere/${PN}-${PV}.tar.gz ?

  From what I've undertood of the portage code, it first try to download
the tarballs from the mirrors (those that are mentionned by GENTOO_MIRRORS
variable in /etc/make.conf). If it can't be found on those mirrors, it
then it download it from the original place (as indicated by the SRC_URI
variable in the ebuild).

-- 
Defresne Sylvain

Re: [gentoo-dev] Smalltalk/X

[Karl Trygve Kalleberg]

On Sun, 9 Jun 2002, Marko Mikulicic wrote:

> I don't understand. Does this mean that those packages cannot be
> download from the original url but only from your mirror. This
> solves a problem, but raises other: if the package is not in the mirrors,
> or the mirror is down, or the package is not yet in CVS ?

As you can specify a sequence of mirrors in /etc/make.conf, it is less
likely that our mirrors will be down than that
djs.ddid.shf.in/~varajana/tmp/tmp/foo/foo/tmp.tgz will be :P

>   This means that while I'm writing the package I cannot test it
> completly (at least not the download) until it is copied to the mirrors.

That is a correct, but should be considered a minor matter, as this step
will be performed by the developer committing your ebuild for you.

>   What SRC_URI should I put in the .ebuild ? Only 
> http:/nowhere/${PN}-${PV}.tar.gz ?

I guess that is okay. http://www.ibiblio.org/gentoo/${PN}-${PV}.tar.gz is
also okay, as this (most likely) is where the package will reside (before
it is spread to our mirrors. 

In fact, I think just "${PN}-${PV}.tar.gz" should work, but I have not
tested that.

Karl T