Re: [Slackbuilds-users] How to get source hostet?
On Wed, Jun 29, 2011 at 4:34 AM, Morten Juhl-Johansen Zölde-Fejér < mj...@syntaktisk.dk> wrote: > On Tue, 28 Jun 2011 07:25:00 +0100 > David Woodfall wrote: > > > But as I see it source checkouts are liable to break from time to > > time. A SlackBuild IMHO should always point to a tested/working > > source. > > Which is why checking out a specific revision would yield the same > result at pointing at a tarball over HTTP/FTP? I fail to see the > difference in anything but ports and agent. I was considering it for > Umplayer as well. > Much worse with a package like Chrome where 'latest' is a moving target > to say the least. > That's not necessarily true. History in a repository can be re-written so even a specific revision could change over time. > > > Having said that I do keep a few dynamic SlackBuilds in my own repo, > > with a big warning about what they do and suggesting that users > > keep a backup of the last, previously working packages. > > I have often thought that if one has builds that do not entirely follow > SlackBuild requirements but otherwise follow the conventions, it would > be nice to be able to search for. But of course, while having > such a database would be a godsend, keeping it current would be a slice > of purgatory... > > > D. > > All the best, > Morten > __ > Morten Juhl-Johansen Zölde-Fejér > mj...@syntaktisk.dk * www.syntaktisk.dk > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
On Tue, 28 Jun 2011 07:25:00 +0100 David Woodfall wrote: > But as I see it source checkouts are liable to break from time to > time. A SlackBuild IMHO should always point to a tested/working > source. Which is why checking out a specific revision would yield the same result at pointing at a tarball over HTTP/FTP? I fail to see the difference in anything but ports and agent. I was considering it for Umplayer as well. Much worse with a package like Chrome where 'latest' is a moving target to say the least. > Having said that I do keep a few dynamic SlackBuilds in my own repo, > with a big warning about what they do and suggesting that users > keep a backup of the last, previously working packages. I have often thought that if one has builds that do not entirely follow SlackBuild requirements but otherwise follow the conventions, it would be nice to be able to search for. But of course, while having such a database would be a godsend, keeping it current would be a slice of purgatory... > D. All the best, Morten __ Morten Juhl-Johansen Zölde-Fejér mj...@syntaktisk.dk * www.syntaktisk.dk ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Here's my $0.02 From: Chris > To: "SlackBuilds.org Users List" > Date: Tue, 28 Jun 2011 13:31:15 +0800 > Subject: Re: [Slackbuilds-users] How to get source hostet? > I suppose one could provide instructions on how to checkout the source and > then make a tarball out of it. Even automate it with a script and add it as > part of the Slackbuild tarball. I would think this is the way to do it. SlackBuilds should build the package from a locally available source, pure and simple. What if you want to recompile when a dependency changes, there's no need to checkout the source again. It would be very nice of you, though not absolutely necessary, to provide an additional script that checks-out and tarballs the source. But that script would have additional dependencies not directly related to the package (ie.: the source code control system and a network connection - neither of which may be available on my system but that shouldn't stop me from building the package). Obviously it must be clearly stated that your download link identifies where to get the source - not a direct link to a tarball. And there's a few extra manual steps required (getting the source code, tarballing it, generating the MD5SUM). But that's just me! <http://about.me/schultzter> ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
2011/6/28 David Woodfall : > On (10:03 28/06/11), Chris put forth the > proposition: >> >> Well that was a fantastic answer. How about giving me a bit more. Perhaps >> a few specific and valid reasons why this is a no-no as you put it. >> >> All it would take is a few extra lines of code to checkout the source and >> then create a tarball excluding the svn directories. >> >> You could also just build it off the checked out source tree. Copy it over >> to a build directory, and build from there, making a package off the result. > > It makes it very difficult to follow the flow if you top post. > > But as I see it source checkouts are liable to break from time to > time. A SlackBuild IMHO should always point to a tested/working > source. > > Having said that I do keep a few dynamic SlackBuilds in my own repo, > with a big warning about what they do and suggesting that users > keep a backup of the last, previously working packages. I have set of scripts for building wine from a git tree (or any source tree). -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
On (10:03 28/06/11), Chris put forth the proposition: Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it. All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories. You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result. It makes it very difficult to follow the flow if you top post. But as I see it source checkouts are liable to break from time to time. A SlackBuild IMHO should always point to a tested/working source. Having said that I do keep a few dynamic SlackBuilds in my own repo, with a big warning about what they do and suggesting that users keep a backup of the last, previously working packages. D. == Original Message From: Ozan T??rky??lmaz Subj: Re: [Slackbuilds-users] How to get source hostet? Date: Mon, 27 Jun 2011 12:23:02 +0500 2011/6/27 Chris : Why not just add to the SlackBuilds script source checkout and tarball creation. That's a big NO-NO -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -- Don't look back, the lemmings are gaining on you. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Il 28/06/2011 07:31, Chris ha scritto: > Since I am directly checking out the source an md5sum would not be needed as > there is no tarball to verify. That is what the checksum is for, verifying > the source tarball, correct. I think the assumptions is that you guarantee: - on the integrity of the tarball you prepare (you put the md5 you calculate in the .info file); - that you have tested that specific tarball with the slackbuild and it works fine. Repositories are dynamic, you can't be sure that every checkout will build smoothly. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
wrote: > First don't top post OK, have it your way. Not that it make any difference. > SlackBuilds is SBo do not donwload anything. Sources should be simply > ifentified in .info file with a direct download link (but that's not > posible always like TrueCrypto) with md5sums of the download sources, > SlackBuilds build packages automaticly. Their duty is not downloading > source nor checking md5sums. I read the Submission Guidelines at Slackbuilds.org. I saw nothing there that disallows this. I do understand this should not be the norm, but in this case the the source is only hosted by svn, to get it you must check it out. I suppose one could provide instructions on how to checkout the source and then make a tarball out of it. Even automate it with a script and add it as part of the Slackbuild tarball. I suppose a case could be made "Follow our template scripts as much as possible. Deviations are fine where needed, but don't change things to be "more clever" or some such - we like consistency"; however, this is not an attempt at being clever. It is a practical solution IMHAO. Since I am directly checking out the source an md5sum would not be needed as there is no tarball to verify. That is what the checksum is for, verifying the source tarball, correct. It's not really big deal to me, host it as a tarball somewhere or check it out from svn; either way, it's not hosted on SlackBuilds.org. I only offered a suggestion (how I would do it). At least your second answer was a wee bit better than your first. Thanks. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Il 28/06/2011 04:03, Chris ha scritto: > Well that was a fantastic answer. How about giving me a bit more. Perhaps a > few specific and valid reasons why this is a no-no as you put it. > > All it would take is a few extra lines of code to checkout the source and > then create a tarball excluding the svn directories. > > You could also just build it off the checked out source tree. Copy it over to > a build directory, and build from there, making a package off the result. http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-April/005398.html Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
2011/6/28 Chris : > Well that was a fantastic answer. How about giving me a bit more. Perhaps a > few specific and valid reasons why this is a no-no as you put it. > > All it would take is a few extra lines of code to checkout the source and > then create a tarball excluding the svn directories. > > You could also just build it off the checked out source tree. Copy it over to > a build directory, and build from there, making a package off the result. > First don't top post SlackBuilds is SBo do not donwload anything. Sources should be simply ifentified in .info file with a direct download link (but that's not posible always like TrueCrypto) with md5sums of the download sources, SlackBuilds build packages automaticly. Their duty is not downloading source nor checking md5sums. -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it. All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories. You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result. == Original Message From: Ozan Türkyılmaz Subj: Re: [Slackbuilds-users] How to get source hostet? Date: Mon, 27 Jun 2011 12:23:02 +0500 2011/6/27 Chris : > Why not just add to the SlackBuilds script source checkout and tarball > creation. That's a big NO-NO -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
On Sun, 2011-06-26 at 19:22:34 -0400, Ben Mendis wrote: > Also, Github gives you 0.30 GB of disk space with a free account which you > could use for hosting. And bitbucket.org gives you unlimited disk space for hosting repositories and files. -- Audrius Kažukauskas pgpfZQZD7IGDk.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
On 27/06/2011 10:23, Eric Pratt wrote: 2011/6/27 Ozan Türkyılmaz: 2011/6/27 Chris: Why not just add to the SlackBuilds script source checkout and tarball creation. That's a big NO-NO Not trying to be a jerk here, but I'm really curious about why this is a NO-NO. Since you can check out by date or revision number, you can get the same revision for the slackbuild each time. Of course, you could check for the presence of the tarball first and if it's not there, check out the revision. If you have to check out, recursively remove the .svn directories, tarball it, and take an MD5 sum of the tarball. The slackbuild could read the .info file and compare the MD5 sum in the .info file with the MD5 sum of the tarball you just created. (Not quite sure why MD5 validation code isn't already required in all slackbuilds anyway.) If you want this check to be optional, then enable it via variable before running the slackbuild, like MD5VERIFY="Yes" or something like that. So we add a few lines to a pretty standard slackbuild to get the tarball and MD5 sum. Once that's done, we're back to standard slackbuild territory. This seems like a perfectly reasonable way to handle this and avoids hosting home-brewed tarballs. Eric ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ If you want this level of automation of checking md5sums, gpg keys etc. then sbopkg does a wonderful job of that. Keeping the scripts simple makes them easier to maintain and verify (the admins do seem to be busy enough as it is!) and easier to spot errors. There are a few scripts in the repository that have "difficult" sources. For example, the TrueCrypt project doesn't make its source available with a static link, and as such the DOWNLOAD variable in the .info file merely points to the page from which the source can be downloaded. Pierre ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
2011/6/27 Ozan Türkyılmaz : > 2011/6/27 Chris : >> Why not just add to the SlackBuilds script source checkout and tarball >> creation. > > That's a big NO-NO Not trying to be a jerk here, but I'm really curious about why this is a NO-NO. Since you can check out by date or revision number, you can get the same revision for the slackbuild each time. Of course, you could check for the presence of the tarball first and if it's not there, check out the revision. If you have to check out, recursively remove the .svn directories, tarball it, and take an MD5 sum of the tarball. The slackbuild could read the .info file and compare the MD5 sum in the .info file with the MD5 sum of the tarball you just created. (Not quite sure why MD5 validation code isn't already required in all slackbuilds anyway.) If you want this check to be optional, then enable it via variable before running the slackbuild, like MD5VERIFY="Yes" or something like that. So we add a few lines to a pretty standard slackbuild to get the tarball and MD5 sum. Once that's done, we're back to standard slackbuild territory. This seems like a perfectly reasonable way to handle this and avoids hosting home-brewed tarballs. Eric ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
2011/6/27 Chris : > Why not just add to the SlackBuilds script source checkout and tarball > creation. That's a big NO-NO -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Why not just add to the SlackBuilds script source checkout and tarball creation. == Original Message From: Manuel Reimer Subj: [Slackbuilds-users] How to get source hostet? Date: Sun, 26 Jun 2011 14:52:19 +0200 Hello, I would like to create a SlackBuild for "osm2pgsql", which is a tool, required to import OpenStreetMap data to a PostGIS database. The SlackBuild is ready, but unfortunately there are no releases. The source is managed on SVN. I found a source archive on the debian mirrors, but they drop parts of the source, as they split that package. How can I request to get a tar.gz for a SVN release hosted on the slackbuilds.org servers, so my SlackBuild can use this as source archive? Can I upload this together with the SlackBuild itself in my tar.gz file? How to get updated? Can I request another file hosting some months later? Thanks in advance Yours Manuel ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
Also, Github gives you 0.30 GB of disk space with a free account which you could use for hosting. On Sun, Jun 26, 2011 at 6:11 PM, markus reichelt wrote: > * Manuel Reimer wrote: > > > The SlackBuild is ready, but unfortunately there are no releases. > > The source is managed on SVN. > > I hate that too. > > > > How can I request to get a tar.gz for a SVN release hosted on the > > slackbuilds.org servers, so my SlackBuild can use this as source > > archive? > > One option would be to ask 'Tadgy' (on IRC - runs a mirror at > slackware.org.uk, check the site) to host it. One would be to host > it yourself somewhere (since you are using gmx, there's some gmxhome > feature, 10MB space for free - if you are not using that already). > > > -- > left blank, right bald > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
* Manuel Reimer wrote: > The SlackBuild is ready, but unfortunately there are no releases. > The source is managed on SVN. I hate that too. > How can I request to get a tar.gz for a SVN release hosted on the > slackbuilds.org servers, so my SlackBuild can use this as source > archive? One option would be to ask 'Tadgy' (on IRC - runs a mirror at slackware.org.uk, check the site) to host it. One would be to host it yourself somewhere (since you are using gmx, there's some gmxhome feature, 10MB space for free - if you are not using that already). -- left blank, right bald pgpuTvkTJzjF7.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] How to get source hostet?
2011/6/26 Manuel Reimer : > Hello, > > Thanks in advance How big is the tarball? I offer free hosting up to 2MB. -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
