Quoting Chris Bannister (2014-02-14 05:10:05)
> On Thu, Feb 13, 2014 at 12:06:10PM +0100, Jonas Smedegaard wrote:
>> This mailinglist is, after all, a list about developing Debian. If
>> your interest is only in *using* Debian e.g. for own package
>> development, then our debian-user lists are m
On Thu, Feb 13, 2014 at 12:06:10PM +0100, Jonas Smedegaard wrote:
> This mailinglist is, after all, a list about developing Debian. If your
> interest is only in *using* Debian e.g. for own package development,
> then our debian-user lists are more appropriate for that:
> https://lists.debian.o
Hi,
John Holland:
> I set up my repo with debarchiver. Is mini-dinstall a better way to go?
> Maybe I should redo it that way?
>
You might also want to look into reprepro.
--
-- Matthias Urlichs
signature.asc
Description: Digital signature
I set up my repo with debarchiver. Is mini-dinstall a better way to go?
Maybe I should redo it that way?
On Wed, 12 Feb 2014 18:56:20 -0600
Jeff Epler wrote:
> If you have a local apt repository (e.g., with dput and
> mini-dinstall), then after building each package you would install it
> to y
Quoting John Holland (2014-02-12 23:51:11)
> I got some debs built for E 18 not 17 gby oing from the source on
> enlightenment.org and building them on Wheezy. They've been working
> pretty well for me on a couple machines.
Great that you have interest in packaging E18. I dearly recommend you
Thanks everyone! These sound like just exactly the pieces I was looking
for. I'll absorb everything I can and either start a new thread or follow
up on this one with any questions I develop.
On Feb 12, 2014 5:22 PM, "Jeff Epler" wrote:
> If you have a local apt repository (e.g., with dput and min
If you have a local apt repository (e.g., with dput and mini-dinstall),
then after building each package you would install it to your local
repo. (typical commandline: dput local packagename*.changes) If
properly configured, pbuilder can look at the local apt repository and
pick up the -dev depend
On Wed, Feb 12, 2014 at 04:10:25PM -0800, Schlacta, Christ wrote:
>On Wed, Feb 12, 2014 at 2:51 PM, John Holland <[1]jholl...@vin-dit.org>
>wrote:
>
> I got some debs built for E 18 not 17 gby oing from the source on
> [2]enlightenment.org and building them on Wheezy. They've bee
I'm sure this isn't the right way to do it, but I put up the tarballs
and dscs and a couple pages that link to them.
http://www.vin-dit.org/~jholland/tarballs.html
http://www.vin-dit.org/~jholland/dscs.html
You have to build them (and install after building) in the order given
at enlightenment.o
I thought they would be set up automatically when I made the repo. I
just tried to get source with apt-get source from my repo and it said
no source package available. What is the right way to add source
packages to the repo?
On Wed, 12 Feb 2014 16:10:25 -0800 "Schlacta, Christ"
wrote:
> On W
On Wed, Feb 12, 2014 at 2:51 PM, John Holland wrote:
> I got some debs built for E 18 not 17 gby oing from the source on
> enlightenment.org and building them on Wheezy. They've been working
> pretty well for me on a couple machines.
>
Thank you for the suggestion, but I'm strictly attempting to
I got some debs built for E 18 not 17 gby oing from the source on
enlightenment.org and building them on Wheezy. They've been working
pretty well for me on a couple machines.
You might want to look at the E18 situation because many of the
dependencies for E17 have been combined into one tarball th
On Feb 12, 2014 10:19 AM, "Neil Williams" wrote:
>
> On Wed, 12 Feb 2014 10:05:41 -0800
> "Schlacta, Christ" wrote:
> >
> > I don't know how to handle this complex dependency of each package on
> > previous packages in the complex build process
>
> Keep building all packages in a loop, remove the
On Wed, 12 Feb 2014 10:05:41 -0800
"Schlacta, Christ" wrote:
> So I'm working on backporting enlightenment e17 from jessie to wheezy
> since my request to backports went unanswered. Anyway, I believe I've
> found out why.
>
> Enlightenment is comprised of about a dozen packages, each of which
>
14 matches
Mail list logo
