[oss-devel] oss source tarball name
Hannu Savolainen
hannu at opensound.com
Fri Jan 18 00:05:47 EET 2008
Dev Mazumdar wrote:
> Yair K. wrote:
>
>> Hi,
>>
>> Currently, the source tarballs are stored in the following manner:
>>
>> 1) Latest stable tarballs are stored in /developer/sources/stable/$LICENSE/
>> and the name of the tarballs depends on the build number.
>> 2) Older tarballs are stored in /developer/sources/stable/attic/
>>
>> This is a problem for those which use automatic scripts to build oss or
>> package systems which build from source. The latest tarball's name depends on
>> the build number, which means that the script must be updated every time a
>> new build is released. If said script wants to keep using a build after a
>> newer one is released, it still has to be updated, because the directory has
>> changed.
>>
>> I suggest the following:
>> A. A stable filename which gurantees to match the latest build.
>> B. A stable filename which gurantess to match the current build (maybe
>> having a copy already in attic/ ?).
>>
>> Yours,
>> Yair K.
>> _______________________________________________
>> oss-devel mailing list
>> oss-devel at mailman.opensound.com
>> http://mailman.opensound.com/mailman/listinfo/oss-devel
>>
>>
>
>
> Hi,
>
> While I agree with this, how do we specify the build id in the package name?
>
> We can guarantee that whatever is in the stable/$LICENSE is always the
> latest - you will only find ONE bz2 file there.
>
> The other option is we rename as follows:
> sources/stable/oss-4.0-stable-<license>.tar.bz2
> But you never know what version this file is.
>
Maybe we could include a file that contains the build ID (for example
./ossbuildid.txt) and/or a symbolic link to the latest OSS version
(./latest-oss-directory). Would this help?
Best regards,
Hannu
More information about the oss-devel
mailing list