-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok i think needs something independ to conary....
we can add a def checkUpdate(url) method on conary. what check the
version. But i think it must complicated ...
Some cli program its the ideal, why because the program notice we if
exist the new version of package and then do a new bump.
So other problem its alot of packages not are %(version)s so needs some
~ program what we can hacked the version. and check the package
something
from Foresight import Upstream
class AppName(Upstream):
version ="1.2_1.x"
def checkVersion(self,version):
version = version[x:x] # hacked version
and do:
$ python appNameUpstream.py
"your app is version 1.2_1.x and its on http://url";
sooo ?
Eric Lake escribió:
| The thing is how do we implement something like this. It should be
| automated someway. Maybe it could read the addArchive line in the
| recipe and check that for a new version that is higher than the
| version line.This would only have to check against the 2-devel repo
| too since we would first update there and then promote.
|
| On Tue, Aug 5, 2008 at 2:16 PM, Jack Doerner <[EMAIL PROTECTED]>
wrote:
|> I very much like the idea of a debian watch like system (I
|> periodically check my own packages, but they're not official)...
|> Perhaps packages could have a maintainer, but don't necesserely have
|> to... like assigning to distro in jira?
|>
|> Jack Doerner
|>
|> There are worse crimes than burning books
|> One of them is not reading them.
|> -Joseph Brodsky
|>
|>
|>
|> On Tue, Aug 5, 2008 at 12:55 PM, Eric Lake
<[EMAIL PROTECTED]> wrote:
|>> Is there a way that we can create a system like the debian to watch
|>> upstream for new versions being released of packages in the repo?
|>> Debian uses watch files to do this and they have a web site that shows
|>> all of the packages that are behind in version. I'm not really sure
|>> how we could do something like this with the foresight repos though.
|>> The last thing I think that we would want is for the end users to tell
|>> us that a package that they really want to use is not up to date.
|>>
|>> Also, should we create a maintainers list? Something that would assign
|>> a packager / dev to a package. Then that person is responsible for
|>> keeping the package up to date. The hard part would be if the packager
|>> ever left foresight then we would have to have a list of the packages
|>> assigned to them and reassign them to different people.
|>>
|>> --
|>> Thanks,
|>>
|>> Eric Lake
|>> _______________________________________________
|>> Foresight-devel mailing list
|>> Foresight-devel@lists.rpath.org
|>> http://lists.rpath.org/mailman/listinfo/foresight-devel
|>>
|> _______________________________________________
|> Foresight-devel mailing list
|> Foresight-devel@lists.rpath.org
|> http://lists.rpath.org/mailman/listinfo/foresight-devel
|>
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkiYqMIACgkQ/HaI43/WxAFrtwCdFIu6pS5A4oLclu8WP8gOqGCj
j/0AoOyw0uyphWD2QCZZ5XGF7zcKOlzJ
=gwaq
-----END PGP SIGNATURE-----
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel
