El dj 10 de 12 de 2009 a les 21:34 +0000, en/na knuutsen va escriure:
>
> PS: I'm not so firm in compiling. In #205 is that a typical way of
> compiling single debs? Where can i learn more about this?
> Thank you in advance
>
* Once your fix gets some more testing and users keep confirming it
solves the problem without side effects, you might want to look into
proposing the fix for a Stable Release Update (SRU). Here is the
procedure on how to do it -> https://wiki.ubuntu.com/StableReleaseUpdates
El dj 10 de 12 de 2009 a les 21:34 +0000, en/na knuutsen va escriure:
>
> PS: I'm not so firm in compiling. In #205 is that a typical way of
> compiling single debs? Where can i learn more about this?
> Thank you in advance
>
You can learn more about packaging here -> /wiki.ubuntu. com/PackagingGu ide/
https:/
@Sylvain: thanks a lot for the fantastic work on this! A couple of
suggestions:
* You might want to look into integrating your patch in the /wiki.ubuntu. com/PackagingGu ide/PatchSystem s#quilt% 20%28example% %20xterm% 29
gnome-power-manager patch system instead of applying it to the sources
directly. gnome-power-manager is using quilt ->
https:/
20package:
* You might also find PPAs useful as an easier way to provide packages /help.launchpad .net/Packaging/ PPA
to users for testing -> https:/
* Once your fix gets some more testing and users keep confirming it /wiki.ubuntu. com/StableRelea seUpdates
solves the problem without side effects, you might want to look into
proposing the fix for a Stable Release Update (SRU). Here is the
procedure on how to do it ->
https:/
Keep up the great work!