Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#11 ChangeLog head next to snapshot download

closed
nobody
Website (34)
5
2006-06-19
2004-01-26
Maarten Brock
No

In RFE 872250 ganeshaadityan mentioned:

I am not (yet) in the habit of building my own sdcc, I
download windoze binaries. I am not sure whether this
patch would have made it's way into the winbins dated
11th Jan. So I'll wait for the next binaries, download it,
and confirm the results (want to avoid downloading 2.7
Mb twice ;-).

bernhardheld answered:

The head of the ChangeLog is included in each napshot.
The ChangeLog clearly tells you, if the fix made it's way
into the snapshot.

This is very nice, but doesn't solve the problem of
having to download the whole package. So maybe it
would be possible to have the ChangeLog head
downloadable next to the package?

Trying to help improve SDCC,
Maarten

Discussion

  • Borut Ražem
    Borut Ražem
    2006-05-16

    Logged In: YES
    user_id=568035

    The current ChangeLog can be found at:

    http://sdcc.sourceforge.net/snap.php

    on top of the document.

    Does this satisfy your request?

    Borut

     
  • Bernhard Held
    Bernhard Held
    2006-05-16

    Logged In: YES
    user_id=203539

    IMHO we should replace the date in the archive name by the
    build number:
    sdcc-snapshot-i586-mingw32msvc-4173.zip
    instead of
    sdcc-snapshot-i586-mingw32msvc-20060516.zip

    This way you can see from the outside what's inside. The
    snapshot date is also listed in the last colom of the web
    page, so no information (especially for the packagers) is lost.

     
  • Maarten Brock
    Maarten Brock
    2006-05-16

    Logged In: YES
    user_id=888171

    Borut,

    The current Changelog is of no use if you want to know if
    a certain bugfix has made it into a dated snapshot. If I
    fix a bug today at say 08:00 UTC nobody really knows if
    it's in one of todays snapshots or not. The snapshots are
    certainly not ready by that time. The only way to be sure
    is to either download the full package (> 4MB) or wait
    just another day.

    Bernhard,

    Your solution is better, but currently we can not see in
    the Changelog which entry corresponds with which build
    number.

    Am I really asking such a difficult question? The current
    snapshot scripts can build snapshots, upload them to a
    server, update the webpage, etc. already.

     
  • Borut Ražem
    Borut Ražem
    2006-05-16

    Logged In: YES
    user_id=568035

    OK, now I understand what you mean. There is a similar
    enhancement request to put regression test results on the
    web. Probably both requests can be done in the same time.

    > Bernhard,
    >
    > Your solution is better, but currently we can not see in
    > the Changelog which entry corresponds with which build
    > number.

    Maybe we should use both build date and revision number,
    something like:
    sdcc-snapshot-i586-mingw32msvc-20060516-4173.zip

    The revision number can be extracted from the result of the
    svn info command:
    svn info | sed -n -e "s/Revision: \(.*\)/\1/p"

    > Am I really asking such a difficult question? The current
    > snapshot scripts can build snapshots, upload them to a
    > server, update the webpage, etc. already.

    No, the question itself is not a difficult one, but the
    implementation is not so trivial :-(. The build process is
    quite difficult to understand and to manage: the build is
    performed on several machines, the targets built on each
    machine are different too: the documentation is done on one
    machine, the WIN32 cross compilation on the other, the
    packaging of binaries on each machine, packaging of sources
    only on one...

    Just be patient - or do it by yourself...

    Borut

     
  • Bernhard Held
    Bernhard Held
    2006-05-16

    Logged In: YES
    user_id=203539

    > but currently we can not see in the Changelog which
    > entry corresponds with which build number.
    http://svn.sourceforge.net/viewcvs.cgi/sdcc/trunk/sdcc/ChangeLog?view=log
    shows everybody exactly this information, nicely formatted.
    I propose to add this link to snap.php. This is easy and
    this should satisfy everybody.

    > Am I really asking such a difficult question?
    No, the question is easy :-> But it's quite difficult to
    find somebody to implement your ideas ;-)

    Borut,
    I can care adding the revision to the package name. But we
    can't use svn, because it's not available on all platforms.
    It's better to extract it from the ChangeLog. More opinions
    about the new package names?

     
  • Borut Ražem
    Borut Ražem
    2006-05-16

    Logged In: YES
    user_id=568035

    Bernhard,

    > I can care adding the revision to the package name. But we
    > can't use svn, because it's not available on all
    > platforms.

    Yes, you are right.

    > It's better to extract it from the ChangeLog.

    Unfortunately this doesn't work on x86-linux2 machine where
    the linux and WIN32 builds are done: the $Revision$ keyword
    is not expanded in ChangeLog. It seems that the svn client
    is too old :-(

    Borut

     
  • Borut Ražem
    Borut Ražem
    2006-05-16

    Logged In: YES
    user_id=568035

    I forgot to mention:

    As I already wrote I plan to change the build process in the
    way that the sources will be checked out only once to the
    shared directory, which is seen from all platforms. This
    will be done on shell.cf.sourceforge.net machine which has a
    quite new version of the svn client: 1.2.1. All other
    machines will create local build directories using the VPATH
    functionality. In that case the $Revision$ keyword will be
    expanded properly on the source tree, so it can be used to
    create a package name.

    The only problem is to find some time...

    Borut

     
  • Bernhard Held
    Bernhard Held
    2006-05-17

    Logged In: YES
    user_id=203539

    > I can care about adding the revision to the package name.
    Done.

    I changed the snapshot page too. I didn't spend much time in
    finding nice words, I leave this to more talented fellows ;-)

     
  • Borut Ražem
    Borut Ražem
    2006-05-18

    Logged In: YES
    user_id=568035

    Maybe you should read the words of "more talented fellows"
    from time to time: your solution doesn't work.

    The

    svn info https://svn.sourceforge.net/svnroot/sdcc | sed -n
    -e "s/Revision: \(.*\)/\1/p"

    is OK since the sdcc builds are done only on machines where
    the svn client is available.

    Borut

     
  • Bernhard Held
    Bernhard Held
    2006-06-18

    Logged In: YES
    user_id=203539

    Sorry for the late reply. I waited for the availabilty of
    the CF, but finally you were faster than me.
    > your solution doesn't work.
    Yes, I knew that it didn't work at that time. It was
    intended to work after the transition to VPATH.

    BTW: can we now close this RFE? I set it to pending state.

     
  • Bernhard Held
    Bernhard Held
    2006-06-18

    • status: open --> pending
     
  • Borut Ražem
    Borut Ražem
    2006-06-18

    Logged In: YES
    user_id=568035

    Bernhard,

    the snapshot build transition to VPATH is almost complete.
    Today I managed to make builds on x86 Linux, mingw, amd64
    Linux, alpha and solaris.

    Maarten: you are the one who submitted the request, so you
    should decide if the provided solution satisfies your needs.

    Borut

     
  • Maarten Brock
    Maarten Brock
    2006-06-19

    Logged In: YES
    user_id=888171

    Allthough I think that what I requested is easier for the
    regular user I certainly can live with this solution. I'll
    close the request.

     
  • Maarten Brock
    Maarten Brock
    2006-06-19

    • status: pending --> closed