You are not logged in.
i had a kind of neat idea that i think it would be cool to implement for all CVS packages
as the whole point of cvs is to stay up to speed with changes and development progress why not add a post-install script offering you the chance to display the change log?
A simple
: View changelog? (Y/n)
Would cover it. I know viewing the changelog is part and parcel of good cvs usage but sometimes we all need a little prompting...just in case we miss something. It will remove the need for the user to locate the changelog in the cvs source - because the packager will have done it for them.
A bit of standardized code would be best as well i think, to maintain consistency.
So, suggestions on a postcard (I can't do mine today cos i am v busy and not booting into linux so i can't get distracted)
Offline
excellent idea. i support that
Offline
this is a bloody stupid idea and unimplementable
we could provide a link to the changelog on the web tho or something?
Offline
heh, woah - first it's good, now it's bad?
I would just echo the whole changelog in the postinstall script for CVS builds... or copy the changelog to /usr/share/PKGNAME or soemthing
Offline
any method for providing the changelog will be supreme. im sure many ppl like to checkout the new changes before installing new versions.
Offline
how about adding the whole ChangeLog text to pre_install with a little "Still Install [Y/n]?" at the bottom?
just have it return true or false (which will cancel the install)
Offline
phrakture - nice ideas - you have 666 posts - glad that wasn't yesterday...
Offline
i find it a good idea - but when you look at the CVS-entries, you will find a lot of upgpkg: foobar-1.23.456-1 that is in most cases not really usefull info
on the other hand, some pkgs undergo essential changes and the CVS-entry of such an upgrade can be very helpfull!
The impossible missions are the only ones which succeed.
Offline
This request comes up monthly.
I'm for an easier way to see changelogs, though I don't particularly like this implementation.
"Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
Offline
i'm not really talking about all packages - just cvs packages - which are mainly maintained in TURs and UORs - i don't think it needs to be an arch wide pacman adjustment - i was just suggesting the adoption of an unofficial standard - same as i would like to see the use of $cvsroot, $cvsmod and anonmyous:@ in all cvs PKGBUILDs. it would just be nice to have an agreed but unofficial approach that's all
sometimes suggesting things in this forum is a bit like getting a quote from a plumber
"(sucks in breath between teeth) Could be tricky, might be expensive if you know what i mean..."
can't we just get on with it and agree amongst ourselves?
Offline