[csw-maintainers] cannot upload update of class action script texhash package

[Dagobert Michelsen]

Hi Peter,

Am 22.02.2013 um 19:35 schrieb Peter FELECAN <pfelecan at opencsw.org>:
> Dagobert Michelsen <dam at opencsw.org> writes:
>> Am 21.02.2013 um 10:24 schrieb Maciej (Matchek) Bliziński <maciej at opencsw.org>:
>>>> Finally, when I'm writing "luxury" I think to what was suggested by Dag,
>>>> i.e. when using only the "packaging" target on a system which has
>>>> checkpkg activated showing what should be the checkpkg stanza; and this
>>>> is not a luxury but a necessity as we have seen.
>>> 
>>> Some GAR code refactoring will be required around line 1015 of
>>> gar.pkg.mk, so that you can either run or display the checkpkg
>>> command, and you still keep all how-to-run-checkpkg information in one place.
>>> 
>>> Dago, is it doable?
>> 
>> The question is what the workflow would be and what should be done. A good thing would IMHO be
>> 
>> - mgar package
>> - (Edit some stuff)
>> - mgar repackage-CSWjustone
>> 
>> After the individual repackage all packages would be checked together. Checking just one
>> package would IMHO be too dangerous. Additionally, I would remove the target
>>  package-CSWfoo
>> as it indicates it could be explicitly called. Building just one package without the others
>> first is also a usecase I would like to avoid.
>> 
>> Peter, would this be acceptable?
> 
> In principle yes. However, for cas-* packages the work-flow is:
> 
> - package one cas
> - upload the resulting cas which is usually architecture neutral

I have created a ticket so I don't forget the issue when I next work on the code:
  https://sourceforge.net/apps/trac/gar/ticket/76


Best regards

  -- Dago


-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896